Skip to main content
The Statutory Compliance API automates the post-payroll compliance lifecycle — filing statutory returns with government authorities and remitting payments through Cadana’s local payment rails. It builds on the existing Tax Engine, Persons Service, and Payroll API.

Key Capabilities

Automated Filings

Create and submit statutory returns to government authorities across jurisdictions.

Government Remittances

Pay what’s owed through local payment rails with automatic FX conversion.

Compliance Dashboard

Real-time visibility into filing status, deadlines, and requirements across all countries.

Audit Trail

Every action recorded with legislative citations and immutable event history.

Choose What You Need

The Statutory API is modular — use filing, remittance, or both.

Filing Only

Cadana prepares and submits statutory returns. You handle payments to authorities yourself.

Remittance Only

You prepare filings externally. Cadana pays the government authorities through local payment rails.

Filing + Remittance

The full loop. Cadana files and pays.
All three modes use the same API — the difference is which endpoints you call:

The Compliance Loop

1

Calculate taxes

The Tax Engine computes gross-to-net deductions with legislative citations.
2

File statutory returns

Create filings from payroll runs — Cadana determines applicable filing types per jurisdiction.
3

Remit to government

Initiate government payments through local payment rails with automatic currency conversion.
4

Prove compliance

Download filed documents, payment receipts, and audit the full event trail.

How Existing Services Plug In

ServiceWhat the Statutory API Uses
Businesses Service (/businesses)Employer identity: KYB.taxId, registrationId, nationalId, country, address
Persons Service (/v1/persons)Worker identity: taxId, nationalId, socialSecurityId, taxProfile, compensation
Tax Engine (/v1/tax)Gross-to-net calculation results with legislative citations
Payroll ServicePayroll run data — filing creation can be triggered from completed payroll runs
When business or person data is updated upstream, the Statutory API reacts automatically — blocked filings unblock themselves without manual retries.

Filing Lifecycle

Every filing follows this lifecycle:
pending → in_review → approved → submitted → accepted
  |           |                        |
  v           v                        v
blocked    blocked                  rejected
  |           |                        |
  v           v                        v
pending    pending               pending (retry)
  • pending — Created with amounts, being validated
  • in_review — Validated and ready for approval
  • approved — Queued for submission to government authority
  • submitted — Sent to the authority
  • accepted — Authority acknowledged receipt
  • blocked — Missing data or requirements prevent submission
  • rejected — Authority rejected the filing — returns to pending for correction
  • cancelled — Filing was cancelled

Guides


API Reference

Statutory Compliance API

Full endpoint documentation