28 apr

Coresuite Country Package


E-invoicing in Germany: How to implement the obligation with SAP Business One

That Coresuite Country Package (originally from Coresystems, now part of the SAP/Boyum world) is an add-on bundle for SAP Business One that covers country-specific requirements for the DACH region. It closes gaps left by SAP's standard localisation for Germany, Austria, and Switzerland, particularly concerning payment documents, dunning, DATEV interfaces, statutory forms, and industry-standard reporting.

Context

The package typically includes extended dunning with configurable dunning levels, payment advices, balance confirmations, SEPA payment runs with German field requirements, reconciliation lists for tax consultants, DATEV-compatible exports, print header templates for German invoice and credit note formats, and country-specific master data extensions (e.g., mandatory HR fields, industry keys). Technically, the Country Package is based on the Coresuite. Framework and is closely integrated with Customize and Designer — for example, invoice layouts are created as pre-defined Coresuite Designer layouts, which are then adapted to client specifications via Customize. The package is updated in its own release cycles, which are aligned with changes in tax law (e-invoicing, ViDA, ELSTER format changes).

Demarcation

The Coresuite Country Package is not identical to the SAP localisation for Germany, which is included in the B1 standard – it supplements it with functions that SAP does not provide in the basic product. It also differs from the Versino Financial Suite, which pursues similar goals but with its own architecture, its own tables (@VPS_-prefix) and a divergent reporting package. Those using both products within the same client should consciously manage any overlap in reminders, payment advices, and DATEV integrations to avoid duplicate logic and conflicting layouts.


ReAct and RLEF

ReAct and RLEF: How Artificial Intelligence Learns from Real Mistakes — and What Automated Bank Reconciliation in SAP Business One Has to Do with It

This is the fourth instalment in a series on this blog dealing with AI fundamentals in conjunction with SAP Business One...
Service Layer AI as a transactional layer

SAP B1 10.0 FP2608: Service Layer AI as a transactional layer

The SAP Business One Service Layer has previously served predominantly as a passive data provider: applications requested data via OData, each ...
Process Reward Model

Process Reward Models: Why a correct result does not yet prove a correct method

This series continuously examines individual AI basic terms and methods such as the Process Reward Model. The previous episode has ...
Test-Time-Compute-Scaling

Test-Time Compute Scaling: Why a Smaller AI Model Can End Up Winning — and What Supplier Comparison in SAP Business One Has to Do With It

This is a continuation of the series on this blog, which deals with Artificial Intelligence in combination with SAP Business One...
RLHF

RLHF and reward models: AI hype or what the approval process in SAP Business One has to do with it

Key takeaways: The article covers the application of artificial intelligence in the context of SAP Business One and fundamental AI topics. Thanks to ...
AI Webinar

AI – Answers from SAP Business One – without SQL, without IT ticket

Live webinar on 30 July 2026, 14:00–14:30 | Live demo via Microsoft Teams | Duration: 30 minutes „How were the sales...".
Wird geladen …