Excel and CSV data import
Turn supported spreadsheet rows into accounting records with explicit import instructions, target-document choices and processing outcomes through FOR:DATA.
These guides describe the shared FOR:CEO company engine. FOR:AGENT uses MCP for supported operations; examples involving browser forms refer to the included FOR:CEO human workspace. Check live capabilities and authorization before an agent runs a task.
Explain what each row is meant to become
A spreadsheet can represent customers, products, invoices or another supported record shape. Upload the supported file and define the intended target, column meanings and accounting references. The import workflow interprets rows according to those instructions rather than assuming every table is a single document or that a column name alone defines the correct financial treatment.
Review results at the record level
Follow processing progress and inspect the resulting records and errors before considering a migration complete. Test the mapping on a representative sample, particularly for taxes, currencies and repeated source identifiers. The same import capability can support ongoing data entry from files, but it does not make an arbitrary legacy-system export automatically complete or lossless.
What to know before you start
Supported record types, file limits and plan entitlements apply. Review duplicate strategy and source completeness; data import is not a promise of one-click migration of every field from every system.
Practical questions
Should I upload a spreadsheet as if it were an invoice image?
Use FOR:DATA for a table of records. PDF or image document extraction is a separate workflow.
How do I know the import is complete?
Compare the source rows with processing outcomes and created records, including any rejected or unresolved items.
Continue the workflow
AI invoice and receipt processing
Turn supported invoice, bill and receipt files into an accounting workflow with document extraction, record matching and the original attachment kept with the result.
Commerce and payment integrations
Transform supported commerce, payment and file events into the intended accounting records using configured customer, product, tax and document rules.
Chart of accounts and fiscal setup
Organize account references and available country fiscal content before recording transactions, so operational documents have an appropriate accounting destination.