EIS Transmission
BlackZero signs each invoice with JWS, encrypts it, and transmits it to BIR within the 3-calendar-day window. BIR's acknowledgement is archived against the original invoice. You never interact with BIR's API directly.
The pipeline
Six steps, zero manual intervention. The transmission pipeline runs for every invoice, automatically.
Invoice was signed, encrypted, and accepted by BIR. Acknowledgement stored against the original invoice record.
Invoice is queued for transmission. Within the 3-day window. No action required unless the status does not resolve.
BIR returned an error or the 3-day window was missed. BlackZero surfaces the BIR error code and guides the correction and retransmission.
Technical specification
Plain-language explanation of the cryptographic and protocol requirements that BIR mandates for EIS.
Each invoice payload is signed using a per-tenant private key via JWS. This creates a verifiable digital signature that BIR uses to authenticate the transmission source.
The signed payload is encrypted using BIR's registered public key before transmission. Only BIR can decrypt it. This protects invoice data in transit to BIR's servers.
Under RR 8-2022, invoices must be transmitted to BIR within 3 calendar days of issuance. BlackZero transmits as soon as the invoice is posted — typically within seconds.
Each taxpayer TIN has its own signing key pair managed by BlackZero's KMS. Keys are registered with BIR during the PTT onboarding process. Key rotation preserves historical verifiability.
If BIR's EIS API is unreachable, BlackZero queues and retries automatically. A circuit breaker prevents cascading failures. You are alerted if retries approach the 3-day deadline.
Every transmitted invoice and its BIR acknowledgement is stored in WORM (write-once, read-many) compliant object storage. Retention satisfies the 10-year BIR records requirement under the NIRC.
BlackZero handles the EIS pipeline. You post invoices. We transmit them.