Packing list

Integrates Tenka with the Sankhya ERP by mapping entities between the two. The mapping is the critical piece: a wrongly mapped field propagates wrong data in both systems — validate the mapping with one record before turning on the full flow.

Imports and synchronizes master data from an external ERP (v0 = CSV file exported from Sankhya): chart of accounts, profit centers, customers, suppliers and general ledger. The file goes into a review area (staging), where each line is validated and marked as new, update or invalid; only then do you apply it. The link is made by the external code (the record's code in the source ERP), so re-importing the same file updates instead of duplicating.

Imports and synchronizes master data from an external ERP (v0 = CSV file exported from Sankhya): chart of accounts, profit centers, customers, suppliers and general ledger. The file goes into a review area (staging), where each line is validated and marked as new, update or invalid; only then do you apply it. The link is made by the external code (the record's code in the source ERP), so re-importing the same file updates instead of duplicating. — this is the role of the "Sankhya Connector" screen within the platform.

The panel’s indicators stay at the top; below, the standard list with the records behind them — search, filters in the side panel, saved views, columns and export. Click a record to open its form.

The uploaded file goes into a review area (staging): each line is validated and marked as new, update or invalid, and the counters for lines read, new, updates and errors appear at the top of the preview. Nothing is written to the master data until you click Apply import — which asks for confirmation and requires the include permission on the screen. Invalid lines show the reason in the notes column and are simply left out when the batch is applied.

"How do I bring in the chart of accounts, customers and ledger from my ERP (Sankhya) without typing everything again?" — when this question comes up, this is the screen that answers it.

No. The link between the file and the master data is made by the external code — the record's code in the source ERP. Re-importing the same file (or a newer version of it) marks already known lines as updates instead of creating duplicates; only a never-seen external code becomes a new record. Before uploading the file, choose the record type in the selector and check the expected columns shown next to it — each type has its own layout. The history at the bottom keeps recent imports with the L/N/A/E score, and the Open button recovers the review of an old batch.