GUEPARDO e-Invoicing: what it is, what NTT DATA publishes and what stays in your SAP

An NTT DATA product to issue and receive documents, and a decision that is yours

The product, in NTT DATA's words, in ten points

What NTT DATA says about its own product, in ten points, with the date of the reading just below.

The three documents NTT DATA mentions, and where each one has its method

Each document has an official rule and its own method in SAP, on the pages indicated in each card.

NTT DATA publishes the list of documents, not the list of municipalities or of events. Coverage by municipality and by event is a question for NTT DATA, with your case in hand.

Five input channels, one question for each channel

NTT DATA says the five channels apply to electronic or non-electronic documents. For each channel, the decision to use it and the control over it belong to the company.

What NTT DATA states about the capture window, and four questions about it

The stated window is a starting point for the conversation, not a commitment on timing.

According to NTT DATA, the webservice captures documents every 1 hour from SEFAZ and every 10 minutes from city governments (visit on 16/10/2026). These are NTT DATA figures, not DFSpro measurements.

Machine learning on PDF: how to validate before you trust

every automatic reading needs a measure of accuracy and an owner for the error.

NTT DATA lists PDF interpretation by machine learning among the product functions (visit on 16/10/2026). Automatic reading is wrong in some proportion, and the company decides which proportion to accept.

1. 01

   Pick a real sample

   PDFs from suppliers and service providers your company actually receives, including those with poor layout.

2. 02

   Define what counts as correct

   The critical tax fields: CNPJ, amounts, taxes and dates. One wrong field may be enough to reject the document.

3. 03

   Measure with NTT DATA

   Run the sample and record hits and errors by field, with date and owner.

4. 04

   Give the error an owner

   Define who fixes the exception, in how much time and how the fix is recorded.

5. 05

   Keep the evidence

   The measurement becomes acceptance evidence. The scenarios and the evidence follow the design of tax tests in SAP.

Software as a service and integration with SAP: what NTT DATA says and what to clarify

Delivery model and architecture go together. The company decides the architecture, with NTT DATA and IT.

NTT DATA describes the product as software as a service on the AWS cloud, with cloud-native availability and scale. The same page says it integrates with the customer's infrastructure, in the cloud or on-premises (visit on 16/10/2026).

Four counterparts, and what each one publishes officially

The middle column is an official source. The right one is NTT DATA's description.

The ERP originates the document, messaging transmits it and the tax authority authorizes it

Four layers, four owners. Mixing the layers is the source of most blame discussions during an incident.

SAP's NF-e documentation (SAP Help, read on 16/10/2026) describes the integration pattern: the ERP supplies the data the authority requires, and a messaging system communicates with SEFAZ and with customers and suppliers. The company can use a SAP product or another messaging system.

Seven steps of the electronic tax document, and who performs each one

The path comes from the rules and the official documentation, not from the product. It helps locate where a component comes in and where it does not.

Where the rejection comes from, and why who fixes it changes

Knowing the layer of the cause avoids asking the wrong area for the fix. In practice, a rejection asks for the code before it asks for someone to blame.

The full table of rejections is in MOC 7.0, Annex I, in the November 2020 version read on 15/10/2026. Check the current version and the technical note for your layout on the NF-e Portal.

Five questions about contingency, before the day SEFAZ goes down

Contingency is provided for in the rules. What the product does in it, and who decides, are points for your contract and your rehearsal.

MOC 7.0 provides issuance types for NF-e: normal, FS-IA, SCAN, EPEC, FS-DA, SVC-AN and SVC-RS, plus offline contingency for NFC-e (Annex I, read on 15/10/2026). The NF-e Portal reported, on the reading of 16/10/2026, that no state had active SVC-AN contingency and that nothing was scheduled.

Contingency in retail, at very high volume, has its own page: NFC-e in retail with SAP.

Acknowledging an operation is a company decision, even when the event is automatic

Automating the event changes the speed, not who answers for it.

The NF-e Portal offers the recipient acknowledgment service (16/10/2026). The MOC provides a rejection when an NF-e is unavailable for download without acknowledgment (code 633, read on 15/10/2026). A product that captures received invoices touches this event.

Event handling in SAP is in automatic inbound NF-e, CT-e and events.

Elasticity, volume and billing: what to take to the conversation

Elasticity is a product claim. Your company arrives with its own volume, not with the portal's number.

NTT DATA says that, regardless of volume, the solution adapts, with stable traffic and proportional billing (visit on 16/10/2026). To give the conversation scale: the NF-e Portal showed 62.137 billion authorized NF-e and 2.977 million issuers on 16/10/2026. This is a national number, and it does not measure your environment.

Five questions about where documents are kept and how they come back

the tax document is the company's obligation, even when an outside service stores it. The way out must be agreed on the way in.

1. 01

   Format of the stored document

   Ask whether the original authorized XML is preserved and in what format it can be delivered to the company.

2. 02

   Retention period

   Ask how long the product keeps each type of document and what happens afterwards.

3. 03

   Audit access

   Define who in the company and who in the audit may look at the documents, and how access is recorded.

4. 04

   Periodic export

   Define whether the company keeps its own copy, and how the product exports history in bulk.

5. 05

   Contract exit

   Ask how documents return to the company if the contract ends, and within what time.

Six security points to request in writing before you sign

When an outside service processes the tax document, the company still needs to know how the data is handled. The answer is worth more in writing.

Two products with different owners, and what each source allows you to state

The comparison uses only what each owner publishes. Neither is presented as better.

These are two offers from different owners for a similar topic. What the difference means in your environment depends on documents, volume, scope and architecture, and the choice is your company's.

Where issuing and receiving end and the obligations begin

Whoever assesses e-Invoicing often asks whether it also handles SPED. The answer depends on four distinct layers.

NTT DATA links e-Invoicing to EFD-Reinf and to SPED. Which obligation your environment generates through which product is an architecture decision, and it is designed in SAP before buying.

The document layout changes, and the question for NTT DATA has a date and a version

Any issuing and receiving product follows the official layout. What matters for the purchase is when and how.

The tax reform changes fields of the electronic tax document because of CBS and IBS, and the NF-e Portal already carries the RFB and CGIBS acts in its legislation menu (16/10/2026). The topic has its own page: tax reform, CBS and IBS.

The SAP side is in tax reform SAP Notes.

Eight contracting questions, all for NTT DATA

These are questions about scope, service and contract exit.

Six things that an issuing and receiving product does not replace

This is the most common question from buyers: if the product solves it, what is left for the team. What is left is below.

Three situations where the problem is before the transmission

Buying an issuing and receiving product does not fix a failure in records, process or environment. These three appear often.

The product chosen changes speed and control, but it does not change the quality of the data that goes into it. That is why the order matters: data and process first, tool afterwards.

Seven SAP items to have ready before switching on the product

The list applies to any issuing and receiving path, and it is the part that DFSpro designs, configures and proves in SAP.

Six scenarios to prove the flow before you decide

The proof uses your documents and your data, in a test environment. A product description does not play that role.

1. 01

   Normal issuance

   A simple NF-e, from the taxable event to authorization, with the status reflected in SAP.

2. 02

   Provoked rejection

   A deliberately wrong piece of data, to see the code returned, where it appears and who fixes it.

3. 03

   Contingency

   The rehearsal of entering and leaving contingency, with the handling of documents issued in it.

4. 04

   Cancellation and voiding

   The two services provided in the NF-e cycle (SAP Help and NF-e Portal), with authorization and numbering reconciliation.

5. 05

   Receipt with acknowledgment

   A supplier invoice captured, posted and acknowledged, with proof of the event.

6. 06

   NFS-e from a real municipality

   A municipality from the company's portfolio, with withholding and service code, from start to posting.

Each scenario ends with evidence: document, status, posting and who checked. To build the scenarios and the exit criteria, use as a base tax tests in SAP.

Four company profiles, and the first question for each one

the starting point of the assessment changes with the bottleneck of the environment. No profile depends on a specific product.

Six mistakes that show up in the assessment and in the implementation

These mistakes are costly because they are found late, and all of them have cheap prevention.

Five roles, and what falls to each one

When each role has a name before starting, nobody assumes that another area already checked.

Six steps to assess e-Invoicing without losing control

A short roadmap, in the order in which each step depends on the previous one. The final decision is your company's.

1. 01

   List documents and volumes

   Document types, volume per month, peaks, CNPJs and NFS-e municipalities.

2. 02

   Map SAP

   The seven preparation items, with the current status and the owner of each.

3. 03

   Take the questions to NTT DATA

   The questions from the earlier sections, with written answers.

4. 04

   Compare by official source

   What each owner publishes, without concluding beyond it. If the company uses SAP NFE, the DRC path comes in.

5. 05

   Prove in a test environment

   The six scenarios, with evidence and owner.

6. 06

   Record the decision

   Who decided, what weighed and which open item was accepted, with date.

Eight fields to turn the assessment into a documented decision

The decision to buy is the company's, and the record shows what it knew when it decided.

Authorized Channel for GUEPARDO, and the SAP tax layer around it

The SAP part is the one DFSpro designs, configures and proves. The product and its terms belong to NTT DATA.

As an Authorized Channel of NTT DATA for GUEPARDO, DFSpro sells the license, implements and governs the product, which belongs to NTT DATA. To know what e-Invoicing covers and under which terms, confirmation comes from NTT DATA.

Who designs and proves, who decides and who answers

The test shows the behavior of the system. The company decides what to do with each result.

The routine for working together with the company's team is described in how we work with your team.

Who published each piece of information, and when the reading was done

SAP and the tax authority in separate groups. What belongs to NTT DATA appears in the text, attributed to NTT DATA, with the date of the visit.

How the cloud talks to the add-on in SAP

Points from the module presentation that help the IT team ask the right questions before switching on e-Invoicing.

Tell us which documents your company issues and receives and on which SAP

The conversation covers your volume, your municipalities and the state of your SAP, with no price and no commitment on timing.

To go deeper first: electronic tax documents in SAP and GUEPARDO Tax.