Service invoice automation in SAP: NFTS, receipt, withholdings and delivery

Automating the service invoice means closing the cycle, not just reading the XML

Reading the XML is the easy part. The hard work is what comes before and after it.

Eight documents that look the same and are not

The first decision in automation is knowing which document is in hand. Each one triggers a different rule at posting.

Official basis Facts with sources; the last column is the design DFSpro proposes.

Two points weigh in practice. The first: in São Paulo, an NFS-e received from a São Paulo provider is never declared by NFTS (city hall questions and answers). The second: the exempt provider's receipt protects the recipient only if it shows name, municipal registration, address, service description, recipient data and amount. Without that, the recipient answers as if there were no document.

Where the service invoice escapes the routine

A goods invoice has had a single national channel for years. The service invoice still lives with several channels, and it shows in day-to-day work.

The invoice the service recipient issues itself: São Paulo and Salvador

The NFTS is not the supplier's invoice. It is the declaration of the service received, made by whoever hires it, and so it must come from a rule and not from someone's goodwill.

The Electronic Invoice for Service Recipients and Intermediaries was regulated in São Paulo by Decree 52.610/2011, based on art. 10-A of Law 13.476/2002, and replaced the Electronic Service Declaration (Decree 52.610/2011). The city hall's current manual is version 3.1 (manual). Salvador also has an NFTS, integrated with the city's NFS-e system, accessed with a Web Password or certificate, with a maximum declaration deadline of 3 years beyond the current year (Salvador manual).

When the NFTS is due

When the NFTS does not apply

• Service received from a São Paulo provider that issued an NFS-e: never declared by NFTS (questions and answers).
• MEI under SIMEI (individual microentrepreneur): exempt from issuing an NFTS as a recipient (decree).
• Individual: does not declare by NFTS; when responsible for the ISS, issues the payment slip directly in the payment portal (manual).
• Month with no service received: the absence is not declared; it is enough not to issue (questions and answers).

The obligation also applies to public bodies, immune or exempt legal entities and Simples Nacional companies that receive services (manual). For investment funds and clubs, the NFTS is issued by the administrator.

Rules the automation must carry

From the invoice that arrives to the proof that stays, in seven stops

The track shows the order. What matters at each stop is who decides and what evidence is left.

Guidance Process design proposed by DFSpro, with no force of law.

Two stops deserve an explanation. At stop 2, the provider's master data decides more than it seems: Simples Nacional, MEI, professional partnerships and self-employed professionals change what can be withheld and how (questions and answers). At stop 6, the tax bookkeeping of a service received is not a single file. The withheld INSS goes to the EFD-Reinf (a digital return in Brazil's SPED system) through event R-2010, the federal taxes withheld on payments to legal entities through event R-4020, and the ISS goes to the municipality, by payment slip or by invoice, depending on the case. The result of the events feeds the DCTFWeb.

Four channels and one rule: a single destination

Whatever the channel, the invoice goes into the same record, with the same identity.

1. 1

   Query by NSU

   The national channel is the ADN Distribution API. The ADN API manual for taxpayers describes two queries: GET /DFe/{NSU}, which returns the document for the NSU given, and GET /NFSe/{ChaveAcesso}/Eventos, which returns the events linked to a key.

   They serve whoever is the issuer, recipient or intermediary (ADN API manual). The query can use a certificate with the same CNPJ root as the taxpayer, and there is a restricted production environment for testing.

2. 2

   Three official warnings

   The official questions and answers give three warnings that change the design (NFS-e questions and answers). First, for recurring consumption the correct route is the Distribution API, not repeated manual queries. Second, the invoice only reaches whoever queries, giving the last NSU: there is no automatic delivery to the recipient.

   Third, if the query finds no new document, the API requires 1 hour before a new attempt. On the municipality side, each send call accepts at most 50 documents or 1 MB, and the ADN processes the queue in chronological order, so a stuck document holds back the ones after it. That is why an invoice can take time to appear even though it was issued.

3. 3

   National portal

   The national portal is the complement. In Received NFS-e, the recipient sees the invoices in which it is a party, filters by period, provider and status, sees the linked events, confirms or rejects, and downloads the XML and DANFSe.

   Login by CPF or CNPJ and password, digital certificate or GOV.BR account, the last only for MEI (questions and answers). What the municipality publishes on its own portal varies, and the ERP must not assume that one channel replaces the other.

Before posting, the invoice goes through five questions

Withholding is where the most money and proof are lost. Automation must check what the provider reported, not just copy it.

Official basis Text from the official sources; the five questions below are DFSpro guidance.

The five validation questions

1. Is the provider where it says it is? Active CNPJ, regime, municipality of taxation and whether the service falls under the exceptions in art. 3 of LC 116 (the tax is owed to the provider's establishment, except in the listed cases, such as the recipient's establishment in the case of § 1 of art. 1) (LC 116/2003, art. 3).
2. Does the ISS withholding make sense? If the municipality of taxation is not the recipient's, the national invoice cannot carry withholding by the recipient.
3. Are the federal contributions in the right field? Withheld PIS and COFINS added in vRetCSLL, not in vPis and vCofins, which are the provider's own debit and do not enter the net amount.
4. Does the net amount close? vLiq = vServ minus unconditional and conditional discounts minus vTotalRet, which adds social security withholding, IRRF, withheld CSLL and withheld ISSQN (topic 13.2).
5. Is there a floor and an exception? Withholding of PIS and COFINS depends on a specific legal provision (example cited: item 04.03 of LC 116) and on the floor of BRL 10.00, according to the questions and answers; the BRL 10.00 floor for social security withholding looks at the total of the DARF, not each invoice (Reinf questions and answers and topic 13.3).

The practical reading is that no validation needs artificial intelligence to exist. It needs a decision table, clean master data and an owner. Tables by service, by municipality and by regime live in the tax master data; see the page on tax master data. The tax reform changes the service invoice, with IBS and CBS, and the calendar is in tax reform, CBS and IBS.

Deliver the invoice to the recipient and keep the proof

Whoever issues must make the invoice arrive. Whoever receives must keep it. Both ends are part of the same automation.

What the documentation confirms and where development comes in

Part of the service invoice automation is documented by SAP; the rest depends on a project.

Where fiscal ABAP comes in

Fiscal ABAP and customization in this layer are DFSpro's: enhancements, BAdIs and exits, plus reports, under tax governance and in Clean Core. On the service invoice, this work usually shows up in five places, which are DFSpro guidance:

• Withholding and municipality-of-taxation rules at inbound, where the project standard does not cover the case.
• A checking report between the invoice, the MIRO bill and the withholdings, before the close.
• A program that generates the batch NFTS file, in the city hall's layout, and controls the deadline and the payment slip.
• Handling of a later event (cancellation and replacement) that reopens the posting.
• Extraction of data for the EFD-Reinf with the correct withholding by provider and by nature.

DFSpro's role

• DFSpro does not replace the integrator in the general architecture or in choosing the capture or issuing tool.
• It works in the tax layer: what the rule must do, how development implements it and how to prove that it did.
• For those who use GUEPARDO Tax, DFSpro sells the license as an Authorized Channel of NTT DATA, and the conversation about what the tool covers should start from the product's official sources.
• The Clean Core is the integration layer, when the design calls for services outside the core.

Three invoices, three paths and one routine

Fictional examples, only to show how the flow decides. The names, municipalities and amounts are made up for the example.

Scenario A shows a subtle point: in São Paulo, the recipient of a provider from outside the municipality declares by NFTS even with no withholding (Decree 52.610/2011, art. 2, I). Whoever designs the rule as 'if there is an invoice, no NFTS is needed' gets it wrong exactly here. The right rule depends on the provider's origin.

Ten failures that show up and the shortest fix

Each row links the sign to the probable cause and to the action. The actions cited as rules come from the sources; the others are guidance.

Automation readiness by area

Mark what already exists. What is left unanswered is the work list.

DFSpro handles the tax layer of the service invoice alongside the integrator

A consultancy from Curitiba, founded in 2018, focused on SAP Tax Governance and on the tax layer of the project.

The method starts from a sample of the company's real invoices: from each document type and each relevant municipality, the check follows the invoice to the posting, the withholding and the tax bookkeeping, and records where the rule failed. The SAP Tax Diagnostic organizes this check; the SAP Tax Governance program provides the cadence.

Sources for each fact

All sources are official, except the SAP blog (an SAP expert, dated 2020). Deadlines, amounts and versions must be checked in the current source before any decision.

The description of each SAP feature depends on the version and on SAP notes, which require access. Taxes, deadlines and municipal rules change: the current source is the agency's.

Find out how many service invoices your environment receives, withholds and records

The first step is to measure: invoices by municipality, withholdings by type and events after payment. Use the contact page to discuss your case.

To read more first: national-standard NFS-e, automatic NF-e and CT-e intake, electronic tax documents, ancillary obligations and SPED and tax setup.