Government purchase orders and B2G invoicing in QuickBooks Online Singapore
A look at how QuickBooks Online in Singapore handles government purchase orders and B2G invoicing, and the customer setup the workflow depends on.
Sellers to Singapore government agencies have been working out how the country’s e-invoicing network connects to their books. In the Singapore edition of QuickBooks Online, purchase orders from agencies arrive directly through InvoiceNow, and invoices travel back along the same rails. Intuit groups the two halves under separate names: Advanced Ordering covers the inbound purchase orders, and B2G invoicing covers the return trip that gets you paid.
Questions from first-time users cluster around three points: where the orders land, how to structure government customers, and what must be true before an invoice can be paid. The accepted answer on the feature covers all three.
Government orders now arrive inside QuickBooks Online
When a government agency sends you a purchase order, it lands in QuickBooks Online alongside your other inbound documents. The software also notifies the agency that the order arrived, so the acknowledgment happens without any action from you.
To see what has come in, open Settings and choose Compliance centre under Tools. Select the InvoiceNow tab, then Inbound Documents. Government orders carry the document type Purchase Order, and anything waiting on you is flagged For Review. Selecting Review opens a specific order for a closer look.
Prerequisites for B2G invoicing
The accepted guidance is blunt about the gate. Three things must exist before you can invoice the government through InvoiceNow. You need a CorpPass account, an approved supplier record on Suppliers@Gov, and InvoiceNow set up in QuickBooks Online.
That second item is the one that trips sellers up. Invoices from suppliers without an approved record are rejected, so it is possible to do everything right inside the software and still fail outside it. If a sent invoice meets with silence, the supplier record is the first place to look.
Why does each agency need two customer records?
Government invoices route at two levels: the agency, and the department within it. QuickBooks Online models that with a parent customer for the agency and a sub-customer for the department.
The parent, typically a ministry or statutory board, holds the billing address, the agency’s Peppol ID, and its Unique Entity Number (UEN). One agency has one of each, shared by every department inside it. Each department contributes its own business unit code and a contact person, and inherits everything else from the parent. Together those fields aim an invoice at the right agency and the right desk inside it.
The setup takes two passes. In Customer Hub, open Customers & leads and select New customer. Create the agency first, giving it a display name and billing address. Under Additional info, set Customer category to Government. Fill in the agency’s Peppol ID and UEN, both of which are required, then save.
Select New customer again for the department. Tick Is a sub-customer and pick the agency in the Parent customer dropdown. The department then inherits the agency’s address, Peppol ID, and UEN automatically. Add the department’s business unit code and a contact person, and save.
If you are unsure of an agency’s Peppol ID, ask the agency you supply. Where an agency has not registered one, the guidance offers a fallback: send through the Accountant-General’s Department, which forwards invoices to the correct agency.
Turning the order into an invoice
With an order reviewed and the customer pair in place, the rest of the flow follows familiar invoicing with one big difference: delivery happens through InvoiceNow rather than by email or PDF.
Raise the invoice against the department, the sub-customer. The inherited Peppol ID and UEN route it toward the agency, while the business unit code and contact person steer it to the department. Send it through InvoiceNow and the invoice travels back to the agency that issued the order. From there, payment follows the government’s own process. It pays to check that the department on the invoice matches the department that issued the order.
Where does this workflow break down?
The accepted answer points to a short list of failure points. An invoice the agency never sees points to the supplier record on Suppliers@Gov. A misrouted invoice points at the customer setup: a missing Peppol ID or UEN on the agency, or a missing business unit code on the department.
Receipt of a purchase order is acknowledged automatically, but nothing else moves until you review the order yourself. An order left sitting in the inbound list is an order nobody has acted on.
Our read
Most of the heavy lifting here sits outside the software. CorpPass, the approved supplier record, and InvoiceNow activation come first, and the in-product work is mostly a one-time customer setup.
Build the parent and sub-customer pair correctly once. The routine then settles into a rhythm: an order arrives, you review it, you invoice the department, and the invoice goes back out over the same connection. Note that the whole flow is specific to QuickBooks Online in Singapore; sellers elsewhere will not find these tabs at all.