NanoCB turns a single purchase order into the full document chain — contracts, commercial invoices, packing lists and export evidence — with a built-in rule engine for China export tax refunds.
Cross-border sellers run their operations in one system — and are audited as four different legal entities. Finance ends up rebuilding the same shipment folder by hand, every quarter.
Purchase orders, SKUs and quantities sit in a single operating system. Contracts and invoices, however, must be issued by the entity that actually bought and sold the goods.
A first-time export refund review asks for contracts, customs declarations, bills of lading, FX receipts, VAT invoices and more — with continuous coverage periods, not just the shipment itself.
Matching document numbers across four systems, chasing stamped scans, and re-checking amounts is slow, repetitive and easy to get wrong.
A purchase order is the root document. Every contract, invoice, packing list and index is derived from it — with one number threaded through all of them.
Upload the purchase-order export from your operations system (Excel today, API on the roadmap).
NanoCB reads the purchasing entity and routes each order into the right chain: invoice + customs export, or no-invoice procurement.
Purchase contract, export contract, commercial invoice and packing list — amounts, tax split and numbering computed, never copied by hand.
Field-level consistency checks, gap report against the refund checklist, and a hash-sealed evidence package.
PO-20261012-018 · 采购方 = exporter → chain A
├─ YCZ-PO-20261012-018 purchase contract ¥60,632.00 incl. VAT
├─ YCZ-EXP-20261012-018 export contract FOB Shenzhen · USD
├─ YCZ-INV-20261012-018 commercial invoice same number, same amount
└─ PACK-20261012-018 packing list 60 cartons · 1,152 kg · 2.68 CBM
checks: Σ lines + freight = PO total ✔ VAT-inclusive rule ✔ refund estimate ✔
Everything is designed around one question: can you prove this shipment, end to end, on the day someone asks?
Contracts, commercial invoices and packing lists rendered from order data — Simplified or Traditional Chinese, FOB terms, amount-in-words included.
Exporter, offshore trading entity and store companies each get their own documents, from the same order. Routing is a rule, not a spreadsheet.
The 39-item first-filing checklist is modelled per shipment, with mandatory vs conditional items and explicit “not applicable” reasons.
Missing invoices, unmatched FX receipts, inconsistent amounts: surfaced as a worklist instead of being discovered during the audit.
One folder per shipment with an index, a manifest of SHA-256 hashes and a checklist status — ready to hand over.
VAT-inclusive versus exclusive pricing by purchasing entity, estimated refund at the applicable rate, and a clear split between goods and freight.
Handles real exports: merged-cell layouts, continuation rows, voided orders, freight and other charges. Line sums are reconciled against order totals on every import.
soon Email evidence capture, e-invoice (digital invoice) support, OCR for supplier invoices and customs declarations, HS-code refund-rate mapping.
NanoCB never backdates a contract and never generates correspondence that did not happen.
A compliance system that fabricates evidence destroys the very thing it is meant to protect. NanoCB is built around the opposite principle: pull real records together, prove they agree, and show exactly what is missing.
Commercial documents are among the most sensitive files a trading company owns. NanoCB is designed to keep them on infrastructure you control.
Database credentials never reach the browser. The front end talks to the application API, nothing else.
Row-level isolation by purchasing entity, so a store operator cannot see another entity’s supplier pricing.
Deploy in your own cloud account, or run the engine on-premise. No shared multi-tenant document store.
Each generated document is hashed; the package manifest lets a reviewer verify nothing changed after issue.
Multi-store, multi-market operations whose purchasing entity is also their export and refund entity.
Exporters buying from domestic factories and selling to their own offshore entities — where the paper trail must be perfect because the parties are related.
Controllers and advisors assembling first-filing packages, and answering the same evidence questions every quarter.
Share a purchase-order export and we will generate the full document set for it — contracts, invoice, packing list and a checklist gap report — so you can judge the output before anything else.