SAP Business One
SME-tier SAP with no DRC — e-invoicing lands on localisation packs or a partner add-on.
// HIGH-LEVEL ARCHITECTURE
Localisation packs plus a certified partner add-on; no eDocument Framework.
- Invoice posts in B1
- Localisation pack or partner add-on builds the statutory document
- Service Layer exposes the data for an external integration where the add-on does not cover it
- Add-on or middleware transmits to the regulator
- Status stored by the add-on, in UDFs, or externally
Service Layer (REST) and user-defined fields. The DI API for older on-premise estates.
Do not assume S/4HANA DRC patterns transfer — there is no eDocument cockpit. Localisation depth varies sharply by country, and a group running B1 at subsidiaries and S/4HANA at the parent ends up governing two unrelated integration patterns as one programme.
// Key components
- Country-specific localisation packages
- Electronic Document Service (B1 Cloud)
- Service Layer / DI API for outbound integration
- Certified partner add-ons per mandate
- Crystal Reports layouts for the human-readable copy
// Strengths
- Lightweight and quick to deploy for SMEs already on B1
- Service Layer is a clean REST surface for ASP integration
- Localisation packs cover the common LATAM and EU formats
- Lower licence cost than S/4HANA for entities under a group umbrella
// Watch-outs
- No eDocument Framework — do not assume S/4HANA DRC patterns transfer
- Clearance regimes almost always need a partner add-on or middleware; budget for it
- Localisation depth varies sharply by country — verify before committing to a date
- Multi-entity groups often run B1 at subsidiaries and S/4HANA at the parent, so two different integration patterns coexist and must be governed as one programme