SAP Document and Reporting Compliance is SAP's unified solution for statutory reporting and electronic documents, bringing together what used to be separate offerings (Advanced Compliance Reporting for statutory reports, and the e-Document framework for e-invoicing). It does two big jobs. First, statutory reporting: it generates the periodic and digital filings authorities require — VAT returns, SAF-T, EC sales lists and country-specific reports — from your SAP data, with a cockpit to run, reconcile, correct and submit them. Second, electronic documents: it produces invoices and other documents in each country's mandated format and handles the real-time exchange with the tax authority, whether that is clearance (the authority must approve before the invoice is valid) or reporting (the authority is notified as it is issued). The value of one solution covering both is that the same platform, kept current by SAP with compliance content, handles the widening range of country mandates rather than a different tool per country.

It depends on the complexity and volume of your indirect tax. Native S/4HANA determination is perfectly capable for many organisations — if your country footprint is manageable and the rules are relatively stable, configuring tax in SAP directly is simpler, cheaper and one less system to integrate and license. An external engine (Vertex, ONESOURCE, Avalara) earns its place when determination gets genuinely hard: many jurisdictions, complex or frequently changing rate content, US sales-and-use tax with its thousands of tax areas, or a need for the vendor to maintain rate content so your team doesn't. The engine plugs into SAP and returns the determination at transaction time. The honest framing is that this is a cost-and-complexity trade-off, not a one-size answer: you take on integration and licensing in exchange for outsourced, always-current content. We assess it by jurisdiction and transaction profile rather than defaulting either way, because both over-engineering with an unnecessary engine and under-serving complex tax with native config are expensive mistakes.

The mechanics differ by country but the pattern is consistent. When an invoice is created in SAP, Document and Reporting Compliance generates the electronic document in the country's required format and transmits it to the tax authority's platform — directly or through an accredited intermediary. In a clearance model (India's IRN, Italy's SdI, much of Latin America such as Brazil's NF-e, Saudi Arabia's ZATCA phase two), the authority validates the document and returns confirmation — an approval, a registration number, a digital signature or QR code — and the invoice is only legally valid once that clearance comes back, so the response is captured against the document in SAP. In a reporting model, the authority is notified as the invoice is issued but does not gate it. Either way, the exchange happens in real time and the authority's response is stored, so you have proof of clearance for audit. Because each country has its own platform, format and rules, DRC's country-specific compliance content — maintained by SAP — is what makes it feasible to support many mandates without building each from scratch.

This is the real ongoing challenge of tax, and it is why the managed-services side matters as much as the implementation. Two things keep you current. First, SAP delivers compliance content updates for Document and Reporting Compliance — new country formats, changed report layouts, updated clearance rules — which have to be reviewed, tested and applied to your system; they do not just appear. Second, when a country you operate in announces a new e-invoicing or reporting mandate, it has to be onboarded ahead of the deadline: configured, tested against the authority's environment and rolled out. Our AMS engagement is built around this rhythm — tracking the mandate pipeline in the countries you operate, adopting SAP's content updates on a controlled cadence, and onboarding new requirements as planned changes rather than last-minute scrambles. The organisations that struggle are the ones treating each mandate as a surprise project; the ones that cope treat compliance change as a continuous, managed process.

Yes — periodic and digital statutory reporting is one of the two core jobs of Document and Reporting Compliance, alongside e-invoicing. It generates the returns and reports authorities require — VAT and GST returns, EC sales lists, SAF-T files, Making Tax Digital submissions and country-specific reports — directly from your SAP transaction data. Crucially, these are produced from source rather than rebuilt in spreadsheets: the reporting cockpit lets you run the report, reconcile it against the underlying data, investigate and correct discrepancies, and submit — often electronically straight to the authority where digital filing is mandated. The advantage of generating returns from the same system that determined and cleared the transactions is consistency: the return reconciles to the transactions and the e-documents by construction, so you are not explaining why three different systems disagree. It also makes audit far simpler, because every figure on a return traces back to the transactions behind it.