Every regulated market is converging on one pattern: the tax authority becomes a system of record. SAP teams that planned for invoice printing now have to plan for IRN-portal handshakes, signed payloads, QR codes back on the printed invoice, and audit trails that survive a downgrade. The mechanics differ between India GST, KSA ZATCA, and the GCC wave behind them, but the SAP-side architecture is the same shape.
The architecture we deploy
SAP S/4HANA (or ECC, for clients still on the previous baseline) emits the invoice over a custom RESTful API exposed through SAP Integration Suite. Cloud Integration handles the canonical transform to the portal's schema, signs the payload, and forwards to the ASP / GSP. The IRN, acknowledgement number, and QR string travel back over the same flow and update the SAP document before the print job is released.
Why Integration Suite, not point-to-point
- Auditability is built in: every iFlow run has a trace, payload, and outcome. Compliance audits stop being a fire drill.
- The portal API changes more often than you would like. Insulating S/4 behind an iFlow means schema drift is a one-iFlow problem, not a Z-program rewrite.
- Re-using the flow across markets becomes a configuration job, not a redesign.
What we typically deliver
- End-to-end design - source mappings, portal schema, retry / DLQ behaviour, certificate management.
- Cloud Integration iFlows, including the parking-pattern for failed IRN responses.
- Side-by-side BTP extensions when the standard ABAP printout needs to render the IRN QR code.
- Cutover runbook: what to test, what to monitor, what the failure mode looks like at month-end.