The FastClose engine can connect to both relational and OData ERP databases, so adding an ERP is connector work (using opur FastConnect technology) rather than a new product. Four are supported today beyond our two primary platforms — and where the report you need doesn't exist yet, we build it with you at no cost.
Rather than a wall of ticks, this is the honest state of each platform. Anything not shipping today is a build-with-you conversation, not a no.
| FINANCIAL REPORTING | OPERATIONAL REPORTING | FASTCHARTS | FASTMIGRATE | |
|---|---|---|---|---|
| Epicor Kinetic | Yes | Yes — deepest library | Yes | Yes — XL Connect and BAQ |
| SAP Business One | Yes | Built with you | Yes | Not applicable |
| Nextworld | Yes | Yes | Yes | Not applicable |
| Acumatica | Yes | Built with you | Yes | Not applicable |
| Business Central | Yes | Built with you | Yes | Not applicable |
| SAP Business ByDesign | Yes | Built with you | Yes | Not applicable |
Not a professional-services quote. The report becomes part of the product, so we are paid by every customer who gets it next. That is only possible because Core reads the ERP directly and building a report is configuration rather than development.
Usually a spreadsheet somebody rebuilds every month. That is the specification.
Configured on your live ERP, so you check it against numbers you recognise rather than a sample set.
If it doesn't tie to what you produce today, it isn't finished. Iteration is part of the arrangement.
It joins the standard content for your ERP — and you inherit every report the customers before you asked for.
If it holds its data in a relational database we can usually read it. Tell us the ERP, the version and what you need to report on, and we'll tell you plainly whether it's a connector we have, a connector we'd build, or a no.
Ask about your ERPA connector we have, one we'd build, or an honest no.