Capture documentXML, email, portal and API
By department · Tax
Tax receives invoices all day long. And it still depends on one person's head.
Abstra captures the tax document, classifies it with AI, calculates the tax by rule and talks to the tax authority, municipalities and your ERP, even where there is no API. Auditable, and ready for the tax reform.
The tax pipeline
- 1
Capture
Invoices, tax slips and bills by email/portal
- 2
Classify
Transaction code, operation nature, tax situation and rule validation
- 3
Calculate
State/city/federal taxes and withholdings with deterministic calculation
- 4
File
Filing, tax authority, municipality, SPED and ERP posting
Exceptions do not block: an ambiguous case goes to human review and returns to the flow. Underneath it all: audit, dedup and a shield against fines.
Workflow example · from tax capture to SAP integration · 100% customized per customer
Validate and classifyextract · validate · apply rules
Portal automationRPA when there is no API
Tax reviewhuman on the ambiguous rule
Integrate to SAPupdates fiscal records
SAP and tax obligationsrecords, slips and filings
Dashboard example · real time, connected and 100% customized
Tax capture, validation and integration in one view
Illustrative data for demonstration.
classified
last 30 days
Docs captured
6,1 mil
Auto-classified
89%
Auto-corrected
184
In tax review
312
Pending tax slips
47
Integrated to SAP
5,1 mil
Month pipeline
From capture to integration
- 01
Captured
6,1 mil
XML, email and portal
- 02
Auto-classified
89%
configured rules
- 03
Auto-corrected
184
tax or address adjustment
- 04
Sent to review
312
code / ambiguous rule · with AI suggestion
- 05
Integrated to SAP
5,1 mil
records updated
Mix
How docs closed this month
- Auto-classified89%
- Auto-corrected3%
- Tax review5%
- Portal / RPA3%
By channel
Capture source
- XML4,8 mil
- Email820
- Portal310
- API170
7-day volume
Integrated vs. in review
OkReview
Mon
Tue
Wed
Thu
Fri
Sat
Sun
Live queue
Items that need attention
- Portal
FX-771
Service invoice · Campinas
Incomplete portal extraction · operation nature missing
AI suggestion · Use nature 1.05 from the vendor master · approve or enter another
- Review
FX-402
Code 5.102 × operation
Ambiguous classification · awaiting tax confirmation
AI suggestion · Apply code 5.102 with CST 00 · approve or pick another code
- Corrected
FX-088
Invoice · tax and address
ICMS ST and recipient ZIP adjusted by rule · no human queue
AI suggestion · Automatic correction applied · review the trail if needed
What tax automation is
Tax automation is the pipeline that captures invoices and tax slips, classifies transaction codes and operation nature by rule, calculates state, city and federal taxes and withholdings, and delivers filings, SPED and ERP posting with an audit trail. With Abstra, classification and calculation are customized per customer; the tax authority and municipalities connect via API or agent when there is no integration.
Proof in tax
Less typing. More on-time tax calculation.
Invoice issued and controlled end to end
In the Westwing case, emails, XMLs and spreadsheets feed issuance, returns, cancellations and SEFAZ tracking, without typing document by document.
Billing and taxes consolidated in one dashboard
At BeFly Holding, tax data from multiple companies consolidates PIS/COFINS calculation, branch analysis and management exports the tax team uses day to day.
If your tax process looks like this, we fix it.
“I receive invoices by email all day long and someone has to download, read and type each one in.”
“Finding the right transaction code / operation nature depends on one specific person's head.”
“Matching what was filed against what was paid takes hours every month.”
“The municipal portal has no API: it's manual login, captcha, one at a time.”
Classification and calculation
Classification and calculation customized to how your operation works.
Transaction codes, operation nature, tax situations, withholdings and filing layouts vary by company. We build the pipeline the way tax already works and connect the tax authority, municipalities and ERP with evidence of what was downloaded, calculated and submitted.
Transaction code, nature and tax situation by versioned rule
Classification stops living in one person's head. Ambiguous cases become human review; learning returns to the pipeline with an audit trail.
See processDeterministic calculation by operation
State, city and federal taxes and withholdings follow your tables and contracts. Mismatches become exceptions with a cause, not a parallel spreadsheet.
See processTax authority and municipalities, with or without API
Issuance, download and tracking of invoices via API when available; RPA or browser agent when the portal requires login and captcha.
See processSPED and obligations with checks before submission
Positional layout, tax-slip vs. return cross-check and a compliance queue before filing with the authority or posting to the ERP.
See processWhere to automate first
How tax calculation and tax-authority filings work
Calculation, filings, obligations, compliance, planning and audit. Start with the process that hurts most today.
Tax calculation
Deterministic calculation of state/city/federal taxes and withholdings by rule.
See processFiling issuance
Generates and organizes filings on time, with a trail of what was issued and paid.
See processAncillary tax obligations
SPED and other filings with layout checks before submission.
See processRegulatory compliance
Cross-checks, alerts and evidence so you don't discover the fine later.
See processTax planning
Scenarios and organized bases so the team decides with trusted data.
See processTax audit
Tax-slip vs. return matching, discrepancies and a full trail.
See processAbstra vs PDF reader, RPA and ERP tax module
What changes when the pipeline must calculate by rule, talk to the tax authority/municipality and leave a trail.
| Criterion | Abstra | PDF reader / generic AI | RPA only | ERP tax module |
|---|---|---|---|---|
| Classification and calculation | Transaction codes, nature and taxes by operation rule | Extracts document text | Depends on the recorded script | ERP rules, little flexibility outside it |
| Tax authority / municipality | API or agent with download/issuance trail | Out of scope | Script per portal | Depends on the vendor connector |
| SPED and obligations | Layout, checks and queue before submission | Does not generate positional file | Possible, brittle to UI changes | Native if the ERP covers the obligation |
| ERP write-back | Posting with idempotency and audit | Delivers spreadsheet or JSON | Clicks through the ERP UI | Native, locked to the vendor |
| Best for | Multi-entity tax with house rules and portals without API | One-off document reading | Portal with no API, low volume | Operations fully inside one ERP |
Integrations
Connected to the ERP, tax authority, municipalities and capture channels tax already uses.
Classification, calculation, filings, SPED and ERP posting. Native connector or browser agent when the portal has no API.
200+ connectors and custom integrations
SAP
ERP
Microsoft Dynamics
ERP
Oracle
ERP
TOTVS
ERP
Qive
Tax
SAP
ERP
Microsoft Dynamics
ERP
Oracle
ERP
TOTVS
ERP
Qive
Tax
Google Sheets
Spreadsheets
NetSuite
ERP
Microsoft Excel
Spreadsheets
Omie
ERP
Gmail
Google Sheets
Spreadsheets
NetSuite
ERP
Microsoft Excel
Spreadsheets
Omie
ERP
Gmail
PostgreSQL
Data
BigQuery
Data
Snowflake
Data
PostgreSQL
Data
BigQuery
Data
Snowflake
Data
Beyond named cases
Real tax patterns
Large e-commerce company
Smart invoice issuance: monitors the tax inbox, determines the transaction code and issues it via the tax authority's API.
Tax BPO
Tax-slip vs. tax-return matching via OCR (corporate income tax), with a discrepancy report.
Industrial company / holding
Generates the corporate tax return's Block M: reads the income-tax spreadsheet and produces the file in the tax authority's layout.
Services (actual-profit tax regime)
Withholding-tax calculator (federal and municipal taxes) on service invoices.
Tax automation needs to classify by rule, calculate tax, talk to the tax authority and municipality and leave an audit trail. A PDF reader stops at extraction.
Why not generic AI?Frequently asked questions
Can you customize classification and calculation for our operation?+
Yes. Transaction codes, operation nature, tax situations, withholdings and routing follow the company rule. The pipeline is built per customer; ambiguous cases go to human review with evidence.
Does it work with municipalities that have no API?+
Yes. We use RPA/browser agents when the portal requires login and captcha, with a trail of what was downloaded and issued.
Do you replace my tax ERP?+
No. Abstra does not replace Protheus, SAP, Omie or Conta Azul. It acts as the pipeline that captures, classifies, calculates and posts into the ERP you already use.
Does transaction-code classification stay in someone's head?+
It becomes a versioned rule. Ambiguous cases go to human review and the learning returns to the pipeline.
Is it just an AI PDF reader?+
Reading the document is one step. Tax needs rule-based classification, tax calculation, filing/SPED generation, talking to the tax authority or municipality and ERP write-back with a trail.
Are you ready for the tax reform?+
The pipeline is built to change rules and connectors without redesigning the whole process. Start with the highest-volume flows now.
Where should we start?+
With the tax inbox, monthly calculation or the ancillary obligation that slips most. Use the processes below to go straight to the detail.
Execution capacity
Automate without building a technical team.
Abstra specialists map, implement and evolve finance automations with your team. Execution capacity without building an internal technical structure.
- Abstra builds for you
- Your team builds
- Hybrid build
Bring a real tax document. We'll build the pipeline with you.
Inbox, calculation, filing or SPED. A tax demo with your operation's rules.