CSV export
Export on any list or report downloads the rows exactly as you see them, with the current search and filters, names instead of codes, and formatted dates. The file opens straight in Excel, Cyrillic included.
How lists workIntegrations and data exchange
Every list and report in BusinessIntents exports to CSV, and every document prints to PDF. BusinessIntents has no public API and no ready-made connectors: integrations with other systems are built by the codbex team as Custom work.
Tell the team which system, which records, and which direction you need. The team reviews the case and sends a scope and a quotation.
Describe the integration at office@codbex.com: the other system, the records, the direction, and how often data should move. Never send passwords or access keys by email.
How data moves today
Most everyday data exchange is a file for the accountant, a report for a manager, or a document for a customer. BusinessIntents covers these with CSV export, printouts, PDF copies, and email on every list, report, and document. Direct connections to another system, such as a bank, an online shop, or an external accounting package, are not available as ready-made connectors. When a customer needs one, the codbex team builds it on the integration services of the codbex platform.
In every subscription
These outputs work in the Free Demo and in Standard, with no extra setup.
Export on any list or report downloads the rows exactly as you see them, with the current search and filters, names instead of codes, and formatted dates. The file opens straight in Excel, Cyrillic included.
How lists workEvery document prints to a branded layout in Bulgarian or English and can be saved as PDF. Issuing an invoice stores a versioned PDF copy on it automatically.
Open templatesInvoices, payment reminders, payslips, and notifications are sent by email from BusinessIntents through Amazon SES in the EU.
Review data hostingCustom work
When a file is not enough, the team scopes, builds, and maintains the connection.
There is no self-service import. Bulk loading of customers, suppliers, products, and other records is done by the team as part of a migration; small volumes can be entered by hand.
Plan a migrationA link to a bank, an online shop, an e-invoicing service, or another business system is analysed, built, tested, and maintained by the codbex team under a separate quotation.
Each customer has its own database in AWS Frankfurt. How the other system signs in, and what it may read or change, is agreed and documented in the scope before anything is connected.
Review securityScoping an integration
Each Custom integration starts with these answers, so both sides know what is built and who looks after it.
Which system, which records (for example customers, invoices, or stock), and in which direction the data moves.
How often data moves, in what volume, and what happens when the other system is unavailable.
How the other system signs in, what it may read or change, and where its access credentials are kept. Nothing is connected before this is agreed.
Which cases are tested, and who confirms that the integration works before it runs on live data.
Who monitors the integration, how changes on either side are handled, and what development and maintenance cost. All of this is set out in the quotation.
Continue the evaluation
Continue with the platform, data migration, security, and pricing.
See how records, roles, and outputs connect inside BusinessIntents.
Open page →Data readinessPlan the bulk loading of your existing data.
Open page →Risk reviewReview access, hosting, privacy, and suppliers.
Open page →Commercial scopeSeparate the subscription from integration work.
Open page →Decision-stage questions
No. BusinessIntents does not offer a public API. When another system needs to exchange data with BusinessIntents, the codbex team builds the integration as Custom work.
There are no ready-made connectors. Data leaves BusinessIntents through CSV export, printouts and PDFs, and email; any direct connection to another system is built on an agreed scope.
Export: every list and report exports to CSV with the current filters, ready for Excel. Import: there is no self-service import; bulk loading is done by the team as part of a migration, and small volumes can be entered by hand.
It depends on the systems and the scope. The team sends a quotation that covers analysis, development, testing, and maintenance.
Next step
That is enough for the team to scope the integration and send a quotation.
Describe the integration at office@codbex.com: the other system, the records, the direction, and how often data should move. Never send passwords or access keys by email.