1. Entity and applicability
Which entity, registration, tax status, timeline, and current official requirement does the client or adviser confirm?
Finance-system discovery
Map InvoiceNow as an operating flow, not a checkbox.
When invoicing requirements touch an in-house or connected system, the useful first step is to trace records, identifiers, validation, exceptions, acknowledgements, reconciliation, and ownership.
Discovery ledger
Nine facts to establish before code.
InvoiceNow is Singapore's nationwide e-invoicing initiative based on the Peppol framework. Current IRAS requirements and implementation pathways must be checked for the specific organisation. Faith Forge Labs can support technical discovery and custom-system work, but does not claim Access Point Provider or InvoiceNow-Ready Solution Provider status.
2. Source transaction
Where are sales and purchase invoices created, approved, amended, cancelled, and retained?
3. Counterparty identity
Which identifiers are captured, who validates them, and how are mismatches corrected?
4. Field contract
Which source fields map to the approved document model, and which transformations need explicit business ownership?
5. Network route
Which approved solution or provider is involved, what interface is available, and where does each responsibility begin and end?
6. Acknowledgements
Which receipts, statuses, errors, or rejections return, and which internal owner must act on each one?
7. Reconciliation
How will transmitted, accepted, rejected, corrected, paid, and posted records be compared?
8. Evidence and access
Which logs are useful, who may inspect them, how long are they retained, and how are credentials protected?
9. Release and fallback
What parallel run, acceptance set, rollback, manual fallback, and support path will protect finance operations?
Architecture choice
Package, connector, or custom layer?
Do not begin with a bespoke integration if an appropriate supported route already exists. Custom work is strongest at a clearly bounded gap that the organisation can own and test.
| Path | Use when | Validate before commitment |
|---|---|---|
| InvoiceNow-ready solution | The finance workflow can live within a supported product | Product fit, provider relationship, data export, support, current official status |
| Supported connector | The source system is retained and a documented connection covers the flow | Interface limits, field coverage, exceptions, monitoring, version ownership |
| Custom boundary layer | A specific in-house workflow cannot use the available route directly | Provider interface, field ownership, test environment, operational support, accreditation boundary |
No compliance promise: a technically successful integration is not, by itself, a legal, tax, accreditation, or regulatory determination.