Connecting, migrating and automating on Sage, answered plainly

We build integrations, automation and small apps for Sage Intacct, Sage 100 Contractor and Sage 300. Typical work: connecting a field service or payroll platform to Sage, scheduling an extract or a journal entry import that someone assembles by hand, adding an approval step Sage does not have, or moving a company into Sage Intacct. Each project is scoped at a fixed price and shown on your own data before it goes live.

Every project gets its own fixed quote. As a guide, from the work we have quoted and delivered so far, in Canadian dollars before tax: a small, contained automation runs $1,500 to $3,000; an integration or larger automation $3,000 to $7,500; a workflow app, such as an approval screen, has been quoted at $6,000 to $10,000. After go-live, the Integration Care Plan is a monthly fee, typically $125 to $175, and apps used by many people can carry a per-user monthly fee instead. Migrations and data loads are quoted once we have seen a sample of the data. More on the home page.

At a fixed price against an itemized scope, agreed before any work starts. The first 30-minute call is free. When the scope is not clear enough to price, we quote a short discovery step first and a firm number after it. The build price does not move unless the scope does.

Mostly how many systems and record types are involved, whether the build writes into Sage or only reads from it, whether data moves one way or both, how clean and consistent the source data is, and how many special cases the rules have, such as tax, fiscal calendars or several companies. So does how much support your team needs while testing.

Small automations and utilities usually take one to three weeks from a signed quote. Integrations and larger automations take three to seven weeks, and workflow apps are typically estimated at four to six. The go-live date often depends on your calendar as much as ours: a year-end, a test window, or the time your team needs to try it on real data.

Usually within two business days of the first call. If something has to be checked first, such as a sample of your data or the other system's API, we say so on the call and tell you when to expect the quote.

Usually half when you sign the quote and half when you accept the finished work. Small jobs may be billed in full on signing. Prices are in Canadian dollars, and invoices are due on receipt.

Your quote says so in writing before work starts. A build made only for you can be handed over with its source code on final payment. When a build starts from one of our own tools, you get a licence to use it and we keep and maintain the shared code. Through a Sage partner, ownership follows the partner's agreement.

If you are on the Integration Care Plan and an update to Sage or the system on the other side breaks something, we fix it. Where Sage offers an API we build on it, because an API changes more carefully than a database does.

It is the monthly support for a build we made, quoted with the build and typically $125 to $175 a month. It covers fixes when an update to Sage or the system on the other side breaks the build, fixes for defects found after the 30-day warranty, and questions about how the build runs. New features and changes in scope are quoted separately. It covers the software we built, not Sage itself: help with using Sage, Sage training and Sage consulting are not part of it.

You can see it. Our syncs and imports log every run. A sync retries temporary errors on its own and shows anything it could not write on its monitor, with the record and the reason. A file import sends back a result log for every file, and a failed file comes back with the reason. You send us the record or the file name and we fix the cause.

We are a small firm, so it is a fair question. Every build is kept in source control with its documentation, and your team gets a written guide to running it. If you own the code, you have the source. If continuity matters for your project, tell us at the quote stage and we will put the arrangement in writing.

When a platform has no native Sage Intacct connector, the connection has to be built directly against its API. The integration reads from the source platform and writes into Intacct through the Web Services API, so the data lands validated and ready to post, on its own schedule. More on the Sage Intacct page.

Yes. Jobber and Housecall Pro publish APIs, and most field and project tools offer an API or a scheduled export, so a direct integration can pull completed jobs, hours, customers and invoices and post them into Sage Intacct without manual export and re-entry. The integration is built around the fields and workflow you actually use. The same approach works for Knowify, CompanyCam, QuickBooks Time, a CRM, a POS or any other system that can hand over its data.

Yes, and it is running in production. A live one-way sync pulls customers, work orders and invoices from Housecall Pro and writes them into Sage 100 Contractor, validated and repeat-safe: re-running a sync never duplicates records, and once a record is posted in Sage the sync never touches it again. Technician hours, service areas and per-line tax come across with the work order. How the sync works.

Yes, both. A scheduled extract pulls trial balance data across your Sage 300 companies, formats it to your consolidation platform's spec and delivers it by SFTP. In the other direction, entry files from payroll or corporate systems are validated against live Sage 300 data and posted as journal entries through the Sage 300 API, with every file logged and archived. Details on the Sage 300 page.

The manual route is to export each data set to CSV and use Intacct's import templates, which have volume and formatting limits and often reject records. The faster route is a direct migration that reads the Sage 100 Contractor database and writes into Intacct through its API. Crossbeam does this, carries historical data as well as current balances, and shows a preview so you can verify the migration before going live.

Use a tool that maps your columns to Intacct's fields instead of forcing your file into a fixed shape. Intacct Workbench works this way: match your columns once, review which records are new and which already exist in Intacct, and import only the rows you tick. A results file shows what posted and what needs a fix.

Sage Intacct has no simple built-in way to change one field across many records at once. Intacct Workbench gives you two paths: select multiple records and apply a bulk edit directly, or export the list, correct the values in Excel and update from CSV. Records in use can be deactivated instead of deleted.

Not natively. Canadian businesses run payroll in a provider built for CRA rules, multi-province tax and remittances, and someone re-keys the journal entry into Intacct each pay period. PaySync removes that step: it turns the completed pay run into a balanced journal entry in Intacct, coded to your accounts, departments and classes, with a preview before anything posts.

Completed work orders have to become invoices before you can bill the client, and by hand that means re-keying the work order into an invoice. Billwright pulls completed work orders from Sage 100 Contractor, builds the invoice lines and totals, and posts the finished invoices back, one at a time or in a batch.

The Stock Item box in 9-2 Parts is not ticked, or was ticked but not saved. Tick it, save with File then Save, then close and reopen 12-2 Inventory Allocation, because screens that were already open do not see the change. If the allocation still will not save, the part has no quantity on hand yet. Our free inventory guide walks through both.

Yes. Sage Intacct exposes a Web Services API that lets custom applications read and write GL accounts, dimensions and transactions. That makes it possible to build connections to other platforms, approval screens, batch tools and reporting feeds that work with Intacct directly.

A connection to Sage Intacct runs under a dedicated Web Services user, not a personal login, with only the permissions the integration needs. On Sage 100 Contractor and Sage 300, what we install runs on your own server under its own dedicated login. In every case you review what it will write, on your own data, before it goes live.

Yes. Much of our work arrives through Sage partners. We work under your project as a subcontractor, by referral with the client contracting us directly for the build, or white label under your brand. See how we work with partners.