Tax, Withholding, and Electronic Invoices

Tax Compliance uses effective legal-entity registrations and posted tax-control accounts. Configure Legal Entities and registrations before creating a return, withholding rule, or e-invoice configuration.

Tax Periods and Returns

Open Tax & Compliance → Tax Period and Return. Filter by legal entity, registration, tax type, status, or period-end range. Columns include registration/entity/branch, tax type, dates/due date, status, output tax, input tax, adjustments, net due, version, and snapshot hash.

Create and prepare

1. Choose New Tax Period.
2. Select an active tax registration and enter start, end, and due dates. The dates must be within registration validity and cannot overlap an existing period.
3. Choose Prepare Return. Forkiva freezes eligible posted output/input tax-control lines into a versioned snapshot.
4. Review transaction date, account, side, journal, amount, scope, totals, and reconciliation against current controls.

Output tax is tax collected on sales and normally owed to the authority. Input tax is recoverable tax paid on purchases. Net tax due reflects output minus eligible input plus adjustments.

Workflow

Open period → Prepare draft → Submit → Approve → Record filing → Settle → Close
                                   ↘ Reject → prepare/correct → resubmit
Filed/Closed → Reopen → new auditable version

Submit freezes maker evidence. Approval is required before filing. Record Filing requires filing reference and date (not before period end). Record Payment / Refund selects a branch in scope, same-currency financial account, settlement date/reference, and evidence; it posts the authority settlement journal. A zero return needs no settlement journal. Close only after a filed payable/refund is settled or the return is zero.

Adjustments

Choose Add Adjustment, search an eligible posted tax-control line, and enter reason, evidence reference, and notes. This includes evidence-backed tax activity in the current return; it does not rewrite the source journal. The line must be posted, in scope, tax-mapped, nonzero, and not already included.

Reconciliation shows snapshot, current control, variance, unreported transactions, and transactions no longer eligible. If evidence changes after preparation, investigate and prepare the appropriate new version rather than ignoring the variance.

Withholding Tax

Withholding means retaining part of a supplier payment to remit to the tax authority.

Rules

Open Withholding Rules → New Rule. Enter registration, code, name, calculation basis (Gross Payment or Allocated Supplier Bills), rate, minimum threshold, effective dates, and Active. Used rules are immutable; create a new effective-dated version.

When a supplier payment uses the rule, Forkiva validates branch/entity/currency/date, calculates final withheld and net cash amounts, posts the withholding liability, and issues a certificate. A supplier is required and withholding must leave a positive net payment.

Certificates and remittance

The certificate list shows certificate number, supplier, payment, rule, date, basis, rate, withheld amount, currency, and status (Issued, Remitted, Void). Open a certificate for frozen rule inputs and journal evidence.

Choose Record Remittance and select one or more Issued certificates with the same branch, registration, and currency. Enter payment account, authority remittance number/date, and evidence. Posting reduces bank/cash and withholding liability. Reverse Remittance posts a compensating journal and restores certificates to Issued; do this before voiding the related supplier payment.

Use Reconciliation to compare open certificate liability with the mapped GL control. A variance normally indicates a missing/duplicate posting, mapping, or scope issue.

Electronic Invoices

E-invoicing prepares issued sales invoices for an installed jurisdiction adapter and retains authority responses.

Configuration

Open Electronic Invoices → Configuration. Select branch, tax registration, installed adapter, environment, secure Secret Reference, and Active. Store only a reference to credentials in a secret manager—never credentials themselves. Use Adapter Diagnostics to review contract version, installed/missing adapter, and validated/review state.

Choose Sandbox for authority testing and Production only for live statutory submission. Changing the environment does not migrate documents or authority references between environments.

Document workflow

1. Choose Prepare E-Invoice and select an eligible issued invoice.
2. Forkiva resolves the effective registration and active adapter, freezes a document fingerprint, and creates an archive record.
3. Submit sends it to the configured authority.
4. If Processing and polling is supported, Refresh Authority Status.
5. Review authority reference, accepted date, adapter/version, submission attempts, result/error, and compliance archive.
6. Cancel Document is offered only for an accepted document and supported adapter; enter the authority cancellation reason.

Document statuses are:

Status	Meaning and next step
Ready	Prepared and eligible for submission after review.
Submitted	Sent to the adapter/authority; wait for its result.
Processing	The authority has not returned a final result; refresh status when supported.
Accepted	Accepted by the authority; retain the reference and acceptance evidence.
Rejected	The authority rejected the document; correct the source or configuration according to the response.
Retry Scheduled	A retryable transport/authority failure is queued; do not submit a duplicate.
Cancellation Pending	Cancellation was requested and is awaiting a final result.
Cancelled	The authority confirmed cancellation.
Failed	Processing ended without a successful authority outcome; review attempt details before acting.

Submission attempts identify the operation as Submit, Poll, or Cancel and the attempt status as Started, Processing, Succeeded, Rejected, Retryable Failure, or Permanent Failure. The compliance archive may contain the Canonical Document, Submission Payload, Authority Response, Acceptance Evidence, and Cancellation Evidence. Access these records only through authorized product controls because they may contain regulated data.

Common Compliance Problems

Problem	Resolution
No effective registration / ambiguous scope	Correct legal-entity branch assignments and non-overlapping registration dates.
Tax controls unmapped	Complete output/input tax mappings before preparation.
Filed return cannot recalculate	Reopen explicitly to create a new controlled version.
Filing reference duplicate	Use the actual unique authority reference.
Withholding rule overlap	End the prior version or choose a later non-overlapping effective date.
Adapter missing/invalid	Install/configure the jurisdiction adapter and pass diagnostics.
E-invoice action unavailable	Use only the action valid for the current authority state.

Authority actions

Filing, remittance, submission, and cancellation can represent real external compliance events. Confirm authority references and evidence before recording them.