Receive Singapore InvoiceNow Invoices in Xero & QuickBooks

To receive Singapore InvoiceNow invoices in Xero and QuickBooks (or MYOB), you need four things in place: an IMDA-accredited Access Point Provider or InvoiceNow-Ready Solution Provider, a Singapore Peppol Participant ID registered in the form 0195:SGUEN<UEN>, that provider connected to your accounting software, and the inbound delivery configured so PINT-SG invoices arrive as draft bills for the bookkeeper to review, code, and approve. Storecove is the most common bridge into Xero. Link4 is the most common bridge into QuickBooks Online. MYOB has InvoiceNow built into its Singapore product natively. Those are descriptive defaults from what is currently in the market, not endorsements; the IMDA-accredited list is broader and worth working through against your own criteria.

The reason this question is operational rather than theoretical right now is the Singapore mandate timeline. From 1 May 2025, newly incorporated companies registering voluntarily for GST were brought into the InvoiceNow requirement. From 1 November 2025, the requirement extended to all newly voluntary GST registrants. From 1 April 2026, it covers newly mandatory GST registrants. Even SMBs that fall outside those issuance dates are being pulled toward enabling the receiving capability by their supplier base — a customer who has gone live with InvoiceNow expects you to receive structured invoices, not to keep asking for a PDF.

The rest of this article walks the practical setup: the difference between an Access Point Provider and an IRSP, vendor-neutral criteria for picking among the IMDA-accredited providers, the operational paths for Xero, QuickBooks Online, and MYOB in parallel, the Peppol Participant ID registration step concretely, the daily workflow once a PINT-SG lands as a draft bill, what is currently available by way of subsidies, and how to keep PDFs and PINT-SG running side by side through the rollout. PINT-SG validation rules and converting the XML into Excel are covered separately in sibling articles, so this one stays on the integration layer.

What an Access Point Provider and an IRSP actually do

An Access Point Provider is the gateway that connects your business to the Peppol network. On the receiving side, it accepts inbound PINT-SG XML on your behalf, validates it, and delivers the parsed data into your accounting software. The same access point can also send outbound invoices once you start issuing under InvoiceNow yourself, but for an SMB whose first concern is suppliers going live, the receiving role is what matters this week.

An InvoiceNow-Ready Solution Provider (IRSP) is an IMDA-accredited solution provider whose accounting or finance software has the InvoiceNow receiving capability either built in directly or wired through a partner access point. According to IMDA's InvoiceNow framework page, Singapore businesses connect to the InvoiceNow network by getting in touch with an IMDA-accredited Access Point Provider, and SMEs can activate InvoiceNow on their accounting or finance software through an IMDA-accredited InvoiceNow-Ready Solution Provider. In practice the two roles overlap — most SMBs end up choosing a single accredited provider that covers both functions for their stack, rather than contracting an access point and an IRSP separately.

The format you are receiving is PINT-SG: Singapore's localisation of Peppol International Invoice (PINT), built on the Peppol BIS Billing 3.0 specification and carried as UBL 2.1 XML. You will not need to read the schema yourself — the access point parses the document on the way in — but PINT-SG and BIS Billing 3.0 are both names you will see in supplier emails, IRSP support tickets, and accounting-software activity logs, so the vocabulary matters.

The network architecture is a Singapore Peppol access point provider for accounting software talking to an equivalent provider on the supplier side, with IMDA sitting above as the Peppol Authority. In Peppol terms it is a five-corner model — sender, sender's access point, receiver's access point, receiver, and the Peppol Authority — and the practical consequence is that you cannot connect directly to the network without an accredited intermediary on each end. Peppol is intentionally not a peer-to-peer protocol; the accreditation layer is what gives the network its trust and addressability.

If the regime itself is unfamiliar, the broader picture — mandate dates, the 5-corner model in detail, why Singapore picked Peppol — is covered in our Singapore InvoiceNow mandate timeline and 5-corner model overview.

Choosing among the IMDA-accredited providers without picking a winner

IMDA publishes the IMDA accredited InvoiceNow Ready Solution Provider list and a parallel Access Point Provider list. Those are reference lists. They tell you who is allowed to operate on the Singapore Peppol network — they do not tell you which provider fits your stack, your inbound volume, your supplier geography, or your audit appetite. Selection is on you, and the criteria below are how to make it well.

IMDA accreditation status. First, before anything else, confirm that the provider you are evaluating appears on the current IMDA Access Point Provider or IRSP list. A non-accredited provider cannot deliver PINT-SG to a Singapore Peppol receiver, and any provider claiming to broker InvoiceNow without accreditation is selling you something else.

Native integration vs middleware bridge for your accounting platform. Native means the provider has built a direct, supported connection into Xero, QuickBooks Online, or MYOB — typically via the platform's app marketplace and using a maintained connector. Middleware means a third-party connector sits between the provider and the accounting software, often as a separately contracted layer. Native is faster to set up, fewer moving parts to break, and the support routing is cleaner when something goes wrong. Middleware is sometimes the only available path for a given platform–provider combination and can be perfectly stable, but it does add a vendor relationship to the diagram.

Pricing model. Per-document, monthly subscription, free tier capped at a document count, or included with the accounting software at no extra charge. The right answer depends on inbound volume and how it grows. For a business receiving a handful of supplier invoices a month, a per-document model or a free tier inclusion can be near-zero cost. Once a couple of suppliers go live and inbound volume climbs into the dozens or hundreds per month, free-tier caps tend to bite quickly and a flat-rate or volume-discounted plan can be cheaper than incremental per-document fees. Run the calculation with realistic supplier-uptake assumptions, not just current volume.

Validation-rule transparency. What happens when a supplier sends a PINT-SG that fails schema or business-rule validation? Does the provider reject silently, surface the error to you with diagnostic detail so you can chase the supplier, or hold the document in a manual-review queue? The answer matters because the day you discover it is the day a real invoice from a real supplier did not land. Ask the provider to show you their failure-handling flow before you sign, not after.

Archiving and audit trail. Inbound XML retention period, ability to download the original Peppol message for an audit, and whether the provider keeps a tamper-evident log of what was received and when. IRAS audits are easier when you can produce the original PINT-SG payload, not just the rendered draft bill in your accounting software. Retention windows vary across providers — some hold messages for a year, some longer, some on a tier you have to pay for.

Geographic coverage. If your supplier base includes Australia, New Zealand, the EU, or any other Peppol jurisdiction, look for a provider connected to multiple Peppol Authorities, not just IMDA. Within the Peppol network, a receiver registered through any accredited access point is reachable from any other — but operationally, a provider that already runs cross-jurisdictional traffic will give you better support when an invoice from an overseas supplier acts up.

Support quality. Singapore-business-hours availability, English-language coverage that goes beyond the front-line ticket, and someone reachable when month-end approaches and a critical supplier's PINT-SG is stuck somewhere. Cheap providers with thin support tend to get expensive on the day a senior bookkeeper spends three hours on the phone trying to clear a single inbound invoice.

This is the framework, not a recommendation. Storecove and Link4 surface most often in Singapore Xero and QuickBooks searches respectively because they have built the strongest single-platform integrations for those products; smaller IRSPs (Advintek, Peppol Express, and others on the IMDA list) cover specific niches that may matter more for some businesses than the dominant names do. Apply the criteria above to your shortlist and the right answer for your stack will surface.

The Xero path — Storecove as the dominant bridge into Bills awaiting review

For a Singapore SMB on Xero, Storecove is the most commonly used bridge for receiving InvoiceNow, and the path to set up an InvoiceNow access point in Xero typically runs through it. Other Xero-compatible IRSPs on the IMDA list follow comparable patterns; Storecove is worked through here because it is the dominant choice in practice and the integration is mature.

The setup runs in this order.

1. Register with Storecove (or your chosen Xero-compatible IRSP) and complete the Singapore onboarding flow. Expect to supply your UEN, your registered business address, and — where the provider supports it — Singpass authentication of an authorised person to confirm the IRSP-side registration.
2. Configure your Peppol Participant ID under your SG UEN. The format is 0195:SGUEN<UEN> and the registration mechanics are walked in detail in the Participant ID section below; for the Xero setup itself, what matters is that the IRSP has the UEN correct before lodging.
3. Authorise the Storecove–Xero connection through Xero's connected-app flow. You sign into your Xero organisation, grant Storecove the permission scope it needs to create draft bills on your behalf, and confirm the connection in Storecove's dashboard. This is a one-time authorisation per Xero organisation.
4. Confirm the network registration. Once Storecove has lodged your Participant ID with Singapore Peppol, you become discoverable on the network. Suppliers' access points can now look up your Participant ID, find Storecove as your receiving access point, and route inbound PINT-SG to you.
5. Run a first inbound test. Ask a cooperative supplier to send a sample PINT-SG, or use a test fixture from Storecove if one is offered. Verify it lands in Xero in the Bills awaiting review state with vendor name, invoice date, line items, GST breakdown, and totals all populated from the XML.

What you see in Xero on day one will be familiar to anyone who already runs Xero AP. Inbound PINT-SG arrives as a draft bill in the same status Xero uses for any incoming bill — pre-populated from the structured XML rather than keyed in by hand or read off a PDF. From there it runs through the Xero bill approval workflow for draft bills awaiting review the same way as any other bill: review, code, approve, pay. The shape of the workflow does not change; only the source of the data does.

For Xero-side specifics — connected-app management, draft bill state behaviour, contact creation rules — Xero Central is the authoritative product documentation. For Singapore-specific Storecove behaviour, the IRSP's own documentation is the source of truth on field mapping, validation handling, and error notification settings.

The QuickBooks Online path — Link4 as the typical Singapore bridge

For QuickBooks Online users in Singapore, Link4 is the most common bridge into the Peppol network. As with the Xero path, other IMDA-accredited providers that support QuickBooks Online appear on the IMDA list, but Link4 is the default that surfaces most often in Singapore-region QBO setups. The pattern of setup is deliberately parallel to Xero — same shape, different account screens.

1. Register with Link4 (or your chosen QBO-compatible IRSP) and complete the Singapore onboarding flow. UEN, registered business address, and authorised-person details are the typical inputs.
2. Configure your Peppol Participant ID under your SG UEN, in the 0195:SGUEN<UEN> form covered in detail below.
3. Connect Link4 to your QuickBooks Online company through the Intuit App connection flow. You authorise the connection from your QBO company file, granting Link4 the permission to create bills.
4. Confirm Peppol-side registration so your QBO company is discoverable on the network. As with any IRSP, this is what allows a supplier's access point to route inbound PINT-SG to you.
5. Test with a single supplier. Confirm a sample PINT-SG arrives in the QuickBooks Online bills list with vendor, line items, GST, and totals populated. From there the bill runs through the standard QuickBooks Online bill approval workflow — the data source has changed, the review-and-approve gate has not.

One thing worth being candid about: QuickBooks Singapore Help and the QuickBooks Community thread on InvoiceNow are noticeably thinner than Xero Central's coverage of the equivalent. If you hit a question about exact field mapping, validation behaviour on an edge case, or how QBO handles a specific PINT-SG tax category code, Link4's own documentation and support team tend to be a faster route to a useful answer than Intuit's documentation. This is descriptive of the SERP and product-doc landscape today, not a comment on QuickBooks itself; the platform handles inbound bills perfectly well, the public documentation just has not caught up with the Xero-side material.

QuickBooks Online is one of the IRAS-listed accounting software options for Singapore SMBs, so adding InvoiceNow receiving fits the existing IRAS-friendly stack without changing accounting platforms. You are extending QBO with a Peppol receiving capability, not replacing it.

The MYOB path — native InvoiceNow with Singapore-specific differences

MYOB Singapore InvoiceNow receiving is structured differently from the Xero and QuickBooks paths because MYOB has built InvoiceNow capability natively into its product. Rather than contracting a separate access point or IRSP, you activate the e-invoicing module from within the MYOB Singapore product itself, and MYOB handles the access-point role on your behalf as part of the subscription.

A few things to confirm before activating.

• You are on the MYOB Singapore SKU, not the Australian product. The two share branding and a great deal of functionality but they are configured for different Peppol jurisdictions — the Singapore SKU registers your participant identity on Singapore Peppol with IMDA as the Peppol Authority; the Australian SKU registers on Peppol Authority Australia.
• Your UEN is current and matches your ACRA / BizFile records. MYOB lodges your Peppol Participant ID in the 0195:SGUEN<UEN> form on Singapore Peppol on your behalf, and a stale or mismatched UEN will fail registration.

The activation itself runs in-product. Enable the InvoiceNow / e-invoicing module from the relevant settings area in MYOB, supply or confirm your UEN, and let MYOB lodge the Participant ID with Singapore Peppol. Confirm the registration through MYOB's in-product confirmation screen, and optionally cross-check through the Peppol Directory (the public lookup is covered in the next section). Once registered, inbound PINT-SG invoices arrive as supplier bills inside MYOB, populated from the structured XML.

The Singapore differences from the Australian MYOB experience are worth holding onto:

• PINT-SG, not PINT A-NZ. The Singapore localisation has stricter rules for IRAS-relevant fields than the Australia/New Zealand variant. A PINT A-NZ document is not a PINT-SG document; the validation rules differ.
• IMDA, not the ATO. IMDA is the Peppol Authority for Singapore; the ATO is the equivalent for Australia. Your participant identity sits with the Singapore registry.
• Singapore GST rules. The current standard rate is 9%; reverse charge applies to certain imported services and low-value goods, customer accounting applies to specified prescribed goods, and zero-rating applies to exports and international services per IRAS guidance. The MYOB tax codes you apply on inbound bills follow IRAS rules, not the Australian ATO equivalents.

The closest operational sibling for Singapore MYOB users wanting to see the Peppol-receiving flow documented in step-by-step form is our Australia-flavoured walkthrough on how to receive Peppol eInvoices in MYOB and create supplier bills. The screen layouts and the underlying activation mechanic are very similar; substitute PINT-SG for PINT A-NZ, IMDA for the ATO, and IRAS GST treatments for ATO GST treatments, and the parallel pattern holds.

For MYOB users running multi-jurisdictional operations — an SG entity and overseas entities on the same group ledger structure — the access-point selection criteria from the earlier section still apply in the limited cases where you would route some inbound traffic through an external IRSP rather than the native MYOB connection. Most SG-only businesses will not need that.

Registering a Peppol Participant ID in the 0195:SGUEN form

A Singapore Peppol Participant ID takes the form 0195:SGUEN<UEN>, where 0195 is the OpenPeppol-assigned identifier scheme for Singapore UEN-based participants and <UEN> is the entity's Unique Entity Number issued by ACRA. An entity with UEN 201234567A, for example, has the Participant ID 0195:SGUEN201234567A. Get the string right: a malformed Participant ID — wrong scheme number, missing SGUEN prefix, transposed UEN characters — is not network-discoverable, and a supplier's access point will report a failed lookup rather than deliver the invoice. You supply the UEN exactly as ACRA holds it; the IRSP assembles the full string.

What you need to register:

• The UEN itself, current per ACRA / BizFile records.
• For most IRSPs, Singpass authentication of an authorised person to confirm the lodgement on behalf of the business.
• Your chosen IRSP to submit the registration to Singapore Peppol on your behalf. You do not interact with the OpenPeppol infrastructure directly — the accreditation layer covered earlier is what makes this an IRSP-mediated step rather than a self-service one.

Timing is usually short. Most IRSPs complete the registration within a few hours; in some cases it takes a couple of business days, depending on internal processing and any verification the IRSP performs. Once registration propagates through the Peppol Service Metadata Locator (the SML, which is the network's directory layer), your Participant ID is discoverable from any other accredited access point on the Peppol network. From that moment, suppliers anywhere on Peppol can route PINT-SG invoices to you.

Verification has two avenues. The first is your IRSP's own confirmation interface — most providers expose a Participant ID status panel in their dashboard showing the registered identifier, the capabilities advertised (PINT-SG receiving, BIS Billing 3.0 receiving, others), and the registration timestamp. The second is the public Singapore Peppol ID lookup directory at peppoldirectory.sg, where anyone can search by Participant ID or by UEN and see what the network knows about a participant — including which document types they are set up to receive. The directory is useful in two directions: confirming your own registration looks right after the IRSP lodges it, and verifying that a supplier is actually network-reachable before chasing them about a missing inbound invoice. If a supplier insists they have sent you a PINT-SG and nothing has arrived, looking up their Participant ID is often the fastest way to find the issue (their registration may not be live, or it may not advertise PINT-SG receiving capability for the document type they are sending).

A common pitfall is worth flagging: a single business should hold one Participant ID, not a duplicate per IRSP relationship. If you have switched IRSPs — say, moved from Storecove to a different Xero-compatible provider, or migrated from a previous accountant who set up an earlier registration — the new IRSP needs to take over the existing Participant ID rather than registering a parallel one under the same UEN. Duplicate registrations cause routing ambiguity on the network and can result in inbound invoices going to the wrong access point. Raise it explicitly with the new IRSP at onboarding so they handle the transition cleanly.

What a bookkeeper actually does when a PINT-SG lands as a draft bill

Once the access point and Participant ID are in place, the daily-life inbound flow looks like this. Your supplier issues an invoice through their access point. The supplier's access point routes the PINT-SG XML to your access point through the Peppol network. Your access point validates the document against the PINT-SG schema and the Peppol BIS Billing 3.0 business rules, and on validation it delivers the parsed data into your accounting software as a draft bill — PINT-SG invoices land as Xero draft bills in Bills awaiting review, as QuickBooks Online bills in the bills list, and as MYOB supplier bills — with vendor, invoice number, invoice date, line items, GST breakdown, and totals already populated from the XML.

What the bookkeeper does next is recognisable but not gone:

• Confirm vendor mapping. If the supplier is new, the system creates a vendor record from the PINT-SG sender details — legal name, UEN, and Peppol Participant ID — and the bookkeeper confirms the new record matches the expected supplier master. For existing suppliers, the access point reconciles to the existing vendor record.
• Confirm GST treatment. Standard supplies at the 9% rate, zero-rated treatments where applicable, reverse charge or customer accounting where IRAS rules require, and import GST for cross-border arrivals. The PINT-SG arrives with a tax category code; the bookkeeper validates that the chosen treatment matches the actual transaction. The XML carries what the supplier asserted; you remain responsible for whether IRAS would agree. The GST-treatment decisions made on each draft bill flow downstream into your quarterly return, so it pays to apply them with the F5 in mind — our walkthrough on how to build Box 5 and Box 7 of the Singapore GST F5 from AP supplier invoices covers the input-tax eligibility gate and import-permit handling that turn coded bills into a defensible return.
• Allocate the GL account(s). The access point cannot do this for new vendors or new spend categories — your chart of accounts is yours, the structured invoice does not know it. The coding decision stays with the bookkeeper.
• Approve. That moves the bill to Awaiting Payment in Xero, the equivalent state in QuickBooks Online, and the equivalent state in MYOB.

The central point is plain: no manual data entry. The fields that previously came off a PDF by hand — or by OCR with a verification step — now arrive structured. The review-and-approve gate the bookkeeper already operates does not go away. It arguably becomes more important, because what is left for the human to do is exactly the judgement work that data entry used to crowd out: new-supplier scrutiny, GST classification, GL coding, and approval routing.

Supplier-side due diligence still belongs in this flow. PINT-SG arriving cleanly does not mean the supplier is who they say they are. Singapore AP teams should still confirm UEN status and GST registration, check the supplier against any internal watchlists, and apply the Singapore AP due-diligence checklist for missing trader fraud risk before authorising payment to a new counterparty. Structured-data inbound channels speed up data entry; they do not change the underlying counterparty controls.

One last point on validation. The access point catches schema violations and a defined set of business-rule failures before delivery — anything that fails validation will not appear as a draft bill at all and will instead surface in the IRSP's exception flow (which is why validation-rule transparency was on the selection-criteria list earlier). Anything that passes validation can still need substantive judgement on the accounting treatment. Conformance is not correctness.

Subsidies and grants for Singapore InvoiceNow adoption

Two programmes have meaningfully subsidised Singapore InvoiceNow adoption: the Productivity Solutions Grant (PSG) and IMDA's InvoiceNow Connect grant. PSG has historically supported pre-approved digital solutions, including accounting software and InvoiceNow-related tooling, for SMBs that meet the eligibility bar. The InvoiceNow Connect grant has at various points covered access-point onboarding and integration costs specifically for SMBs activating the receiving capability. Both have been meaningful contributors to keeping the cost of going live close to zero for businesses that qualify.

What is critical to flag honestly: the precise eligibility criteria, support amounts, and qualifying solutions shift over time and are subject to budget cycles and policy updates. A grant that paid 50% of qualifying costs in one year may pay 70% the next, then revert, then be replaced. Vendor blogs are unreliable for current grant figures because they go stale within months of publication and are rarely revisited.

The authoritative live source is GoBusiness Grants at gobusiness.gov.sg, which holds the current PSG and IMDA-administered grant references and the up-to-date application criteria. For IMDA-administered programmes specifically, IMDA's InvoiceNow framework page is the source of truth for current scheme details.

What an SMB typically needs to apply: a UEN, financial standing in good order (no outstanding tax liabilities or compliance issues), a quote or proposal from a pre-approved solution provider for the IRSP or accounting software being acquired, and a Singpass-authenticated submission. Some programmes require the application to precede the purchase — meaning if you sign and pay first, you may disqualify yourself from the grant retroactively. Check the current rules on GoBusiness before you commit.

Worth keeping in proportion: the cost of an access point or IRSP, even before any subsidy, is typically small relative to the bookkeeper hours saved on manual data entry once inbound PINT-SG volume is meaningful. The grant question is real and worth pursuing if you qualify, but it is rarely the deciding factor in whether to enable receiving — the operational case stands on its own once a couple of suppliers have gone live.

Running PDF and PINT-SG invoices side by side through the rollout

Through the Singapore transition window — and the InvoiceNow rollout has dates pencilled out to 2031 for full coverage — most SMB AP teams will receive PINT-SG and PDF invoices in parallel. Suppliers will go live on InvoiceNow at different speeds. The largest, most digitally mature suppliers are already there. Smaller suppliers and most overseas counterparties (anyone outside the Peppol jurisdictions or not yet activated within them) will keep sending PDFs for the foreseeable future. The operational question is how to run a consolidated PDF and PINT-SG workflow that AP teams can actually live with — not whether the PDFs go away, because they do not, on the timeline that matters for this year and next.

The consolidated workflow looks like this. PINT-SG arrives through your access point and lands as a draft bill in Xero, QuickBooks Online, or MYOB with structured fields populated from the XML. PDFs from suppliers not yet on InvoiceNow can be processed into the same structured shape — vendor, UEN, invoice number, invoice date, line items, GST breakdown, totals — using AI-powered invoice data extraction so the bookkeeper's review and approval step is the same shape regardless of how the invoice arrived. Same fields to check, same coding decisions to make, same approval routing.

The point worth making to the AP team is about cognitive switching cost rather than tool count. The bookkeeper does not want to think "is this invoice in PINT-SG or PDF" before reviewing — they want one review queue with consistent fields and one mental model for what each field contains. Standardising the downstream review surface removes that friction. The inbound channel becomes an implementation detail; the work the bookkeeper does on each invoice is the same.

For teams that want PINT-SG XML out of the accounting software and into a spreadsheet — for spend analysis, sample audits, working with a finance colleague who lives in Excel, or any reason a structured tabular view is more useful than the rendered draft bill — the sibling article on how to convert PINT-SG XML invoices to Excel for AP review walks that path. Two channels in, one review surface, and the option to drop into a spreadsheet whenever the data analysis question warrants it.