From your own data to a reviewed allocation
1. Import evidence from your account
Use the CSV format published in the dashboard or import CFDI Guard evidence from your own account and project when enabled. Format, scope, external IDs and limits are validated; an invalid row rejects the entire import before its data is persisted.
2. Examine explainable proposals
Relate amounts, dates and references using deterministic rules. Each proposal shows its explanation and source evidence; ambiguous matches and discrepancies remain subject to review.
3. Decide and retain a trace
Review allocations and partial payments, then inspect exceptions and balances by currency. Decisions are recorded with version checks; a reminder draft requires approval and is not sent.
Current service configuration
An enabled capability describes published configuration; it does not grant access to your account or guarantee imported data quality. The dashboard checks project, source, validity and budget before each operation.
CSV invoice imports
Checking…CSV imports of declared payment movements
Checking…Import your own project CFDI evidence
Checking…Explainable deterministic proposals
Checking…Human-reviewed allocations and partial payments
Checking…Aging and balances by currency
Checking…Reminder drafts and approval without sending
Checking…Explicit references to your ViciousByte captures
Checking…Private JSON and TXT exports
Checking…ViciousByte evidence signature
Checking…Automatic proof of customer invoice payments
Capture does not prove customer invoice paymentReminder delivery
Delivery not implemented: drafts onlyBank connectors
Bank connectors not implementedCurrency conversion
Currency conversion not supported
What reconciliation establishes
Matches are proposals based on data and rules, not bank confirmations. An amount, date or reference may match for other reasons. Review candidates, exceptions and coverage: limits and truncation can leave other candidates outside the response.
Allocations and partial payments require explicit review. The submitted amount for each invoice–payment pair is its desired total, replacing the previous value rather than adding an increment. Voiding an allocation records a correction; it does not refund money. Balances reflect imported data and decisions, not receipt of bank funds.
Aging is calculated by currency from declared dates up to the as_of cutoff; future payments are excluded. Proposals use the current balance, not a reconstructed historical balance. Different currencies are not added or converted. Imported information does not certify delinquency or bank settlement.
Evidence retains references, rules and decisions. When configured, a ViciousByte signature attests to application report integrity; it does not certify a bank, an actual payment or accounting or tax correctness.
Reminders that remain drafts
Debits, captures, transfers, disbursements and other actions on funds are not executed. Drafts and exports require review before being used outside the service.
Limits and a separate budget
A Receivables pilot has its own reconciliation_attempt quota for reconciliations, separate from CFDI validations, investigation and transcription minutes. Operations also have independent daily admission budgets. The dashboard shows reservations and consumption; no new price is offered and no automatic charge is started.
CSV format: UTF-8 text (initial BOM accepted), comma-delimited, with published headers and no unknown or duplicate columns. Decimal amounts are strings with a dot and no thousands separators; dates use YYYY-MM-DD. Only declared inbound payments are supported: outbound movements and refunds are rejected, not silently netted. External IDs are unique per kind within the project; changing immutable facts for an existing ID causes a conflict rather than an overwrite.
Published limits could not be confirmed. Check the dashboard; available capacity, quota or retention is not assumed.
Private data and retention
Projects and imports belong to one account. Reading, decisions and exports require authorization for that project; knowing an RFC or reference does not grant access. Do not include banking credentials or card data in files.
The dashboard shows the dossier’s shared expiry. Revocation, deletion or expiry blocks corresponding reads and queues data and evidence purging; physical deletion is asynchronous. A closed dossier is not silently recreated in the same project. Minimal quota and idempotency receipts follow separate retention.
Access requires an explicit Receivables pilot approved for your account and project with its own budget. A plan for another service does not enable it. An access request records pending interest without granting permissions or starting payments.
Request pilot access
Register a Reconciliation and receivables request for your account. This does not create a subscription, activate permissions or execute a payment.