Full technical cycle
CUF, XML validated against the official XSD, XMLDSig signature, gzip compression with SHA-256 hash and SOAP submission.
SIAT E-Invoicing
Invoice online without stopping the till.
MKA builds, signs and sends every invoice to the tax authority (SIN), reads the response and warns you before your CUIS or CUFD expire. If the connection drops, the branch enters contingency and packages are sent later.
Without MKA
- You find out the CUFD expired when the till can no longer invoice.
- An invoice rejected by the SIN sits in limbo and nobody knows why.
- When the internet drops, the manual invoice book ends up in a shoebox.
What you’ll measure
Invoices validated on first send
99,2 %+1,6 pts
Invoices issued this month
48,3 K+9 %
Pending contingency packages
0−3
Rejection resolution time
1,5 h−20 h
from rejection to valid invoice
Sample indicators with illustrative data. In MKA they are computed live from your operation.
Try it right here
Try it: issue an invoice, cancel it and issue a credit/debit note.
This is the branch’s invoicing screen. Press “Issue” and follow the path: CUF, XML, signature, compression, submission and response code. Press “No internet: switch on contingency”: the branch keeps invoicing and the invoice waits in a package until the network returns. Cancel, issue a credit/debit note (on an invoice in a package or cancelled, the system won’t allow it) and fast-forward the clock: with the CUFD expired, you can’t issue. “Watch it run” plays it for you.
Example flow
From sale to validated invoice
Step 1/6
The sale is closed
The sale comes from the point of sale or from a back-office order.
Point of sale (POS)Benefits
Why SIAT E-Invoicing in MKA
CUIS and CUFD watched
Validity is checked before issuing and expiry alerts are generated every 6 hours.
Contingency per branch
Entering and leaving contingency, significant events, invoice-book transcription and package sending.
Cancellation and notes
Cancel and reverse cancellations. Issue credit/debit notes only against invoices registered with the SIN.
Printed representation
Letter-size and 80 mm thermal-roll PDF in the official layout.
Admin console
Request log, conciliation, recovery of blocked invoices and sale points, and a dashboard.
In detail
Everything included
Issuing
- CUF generation
- XML validated against the official XSD
- XMLDSig signature, gzip compression and SHA-256 hash
- SOAP submission and interpretation of response codes 901–972
- Letter and 80 mm thermal PDF in the official layout
Cancellations and notes
- Cancellation and reversal of cancellation
- Credit/debit notes (sector document 24) only against invoices registered with the SIN
- Credit/debit note cancellation
Contingency
- Enter and leave contingency per branch
- Significant-event registration and resending of overdue events
- Manual invoice-book transcription
- Package sending of invoices
Codes and catalogs
- CUIS and CUFD validity check before issuing
- Expiry alerts every 6 hours
- Sync of 11 SIAT catalogs in a single action
- Catalog check at issue time
Administration
- Request log viewer
- Conciliation and recovery of blocked invoices and sale points, with batch resolve
- Bulk NIT validation
- Management of digital signatures, tokens and homologations
- Invoicing status dashboard
All-in-One
Connects with
Data flows between modules on its own: no integrations, no exporting or importing.
Point of sale (POS)A fast till that keeps selling and invoicing even when the internet drops.Tax Ledgers & FormsPurchase and sales books that fill themselves.AccountingJournal entries that build themselves from your documents.CollectionsOne payment, many invoices, and receivables aging always current.Orders & shipmentsOrders, partial shipments and consolidated invoicing, all linked.
FAQ
What if a branch loses internet?
The branch enters contingency, the significant event is recorded and invoices are sent in packages when the connection returns. Manual invoice-book invoices are transcribed into the system.
Can I issue a credit/debit note on any invoice?
Only on invoices registered with the SIN. The system won’t allow it against an invoice that wasn’t validated.
Who is responsible before the SIN?
Your company, as the taxpayer. MKA is the tool that runs the technical cycle; tax configuration and tax decisions remain yours and your accountant’s.
More in Invoicing & compliance
See SIAT E-Invoicing with your data.
In 30 minutes we walk through your real flow: from sale to invoice, from stock to journal entry.