Understanding the path matters because every failure you will debug happens at one of these steps.
The sequence
- Your system builds the invoice. Buyer details, items, quantities, rates, tax amounts.
- It is transmitted, as a structured message, to the digital invoicing service.
- It is validated. Is the seller registered and active? Is the buyer's registration valid? Do the tax calculations agree with the rates for those item categories? Are mandatory fields present?
- A response comes back — either a unique invoice number, or a rejection with a reason.
- You print the identifier, typically with a QR code, on the customer's copy.
Steps 2 to 4 happen while the sale is in progress. That constraint drives everything in chapter six about failures.
Where the integrator sits
Integration runs through a licensed integrator — a provider authorised to pass invoices to FBR on behalf of businesses. It sits between your software and FBR:
Your POS / ERP → Licensed integrator → FBR → identifier back
A useful detail that is not widely known: a business may use more than one licensed integrator. If your retail counter runs one system and your wholesale side another, you are not forced to consolidate onto a single vendor first.
What goes in an invoice
Exact field names and formats come from your integrator's specification, but the shape is consistent and worth knowing before you scope the work:
- Seller: registration number, name, address.
- Buyer: registration number where registered, name, and a type indicating registered or unregistered.
- Invoice: your own number, date and time, type (sale, debit note, credit note).
- Each line: description, an item classification code, quantity, unit, value excluding tax, tax rate, tax amount, and any further taxes.
- Totals, which must reconcile exactly with the sum of the lines.
The two fields that cause most rejections
Item classification codes. Each product must be classified to a prescribed code, and the applicable tax rate follows from it. Businesses that have never maintained these have to build the mapping, and that is usually the largest part of the whole project.
Buyer registration numbers. They must be valid and active. Existing customer records are frequently stale — closed registrations, transposed digits, numbers recorded for a different entity — and each one is a rejection at the counter until it is fixed.
Both are data problems rather than software problems, which is why starting the data clean-up before the integration work is almost always the right order.