From a posted invoice to an accepted e-invoice
Invoice as you do today; here is what happens to each posted invoice and how you go live.
Your system
Your provider
Four ways in, whichever your system allows
A small agent on your PC or server
Desktop or on-premises systems like TallyPrime. A Windows service; calls out only.
A cloud connection
For cloud systems: you approve access online; nothing to install.
A read-only database login
For ERPs on SQL Server or Oracle, and systems your own team built. Your IT gives a read-only login; Vattora reads posted invoices only.
An Excel or CSV file
Any system without an interface: export, upload, and Vattora does the rest.
A correct e-invoice, or a clear reason
PINT AE, field by field
Seller, buyer, TRNs, invoice type, dates, line tax category and rate, totals.
Checked before it leaves
Each e-invoice is checked against the PINT AE rules Vattora implements. A problem stops it on our side, with the reason, before your ASP sees it.
Credit notes linked
Credit notes carry the reference of the invoice they correct.
Your ASP does the official exchange. You see everything.
Vattora sends each e-invoice to your provider's API and tracks the answer.
The path from first call to go-live
Readiness check
20 real invoices mapped to PINT AE, gaps listed, written fixed price.
Connection
We connect your system and your ASP. You enter passwords yourself through a one-time secure link.
Test with your ASP
First, real invoices go to its test environment; we check each answer.
Go live
From go-live, every posted invoice follows the path on its own.
See what your invoices need.
Send us 20 real invoices or connect read-only. You get the gap list and a fixed price.