Accounting and ERP integrations

DealJourney connects to accounting and ERP systems so that customers, invoices and payments stay consistent between the CRM and the finance system, rather than being kept in both by hand.

Several are supported, covering the common Nordic systems and Microsoft Dynamics. The definitive list of what your company can connect today is in Marknadsplats, worth checking there rather than assuming either way, since which are available can differ by company.

The accounting system is the authority on money. This is the most important thing to understand about these integrations. Invoices, credit notes and payments belong over there; DealJourney reflects them so that the people talking to customers can see them. That is why some invoices are read-only in the CRM and some actions finish on the accounting side.

Which direction things flow depends on setup. Customers commonly sync both ways, invoices usually come into the CRM, and what happens when the same record changes in both places is a configuration decision. Have that conversation before switching it on, not after the first conflict.

Connecting is an administrator job, and it is company-wide rather than per person. One connection serves everybody.

Expect an initial sync. The first run brings across the existing book, which can take a while and can surface duplicates where the same customer was created independently on each side. That is normal, and it is easier to resolve early than after months of divergence.

Reviewing duplicate Fiken customers. DealJourney can identify customers with the same name and check their invoice history. These are candidates for review in Fiken, not a recommendation to remove them automatically. Fiken may archive a customer instead of deleting it when accounting history exists. Automatic customer removal and cleanup of historical accounting links are therefore unavailable in DealJourney; support can help review a missing link.

Subscription drafts with Fiken. When automatic invoice creation is enabled, new subscription bills, including overdue periods produced by billing, are queued as Fiken drafts using their saved prices, currency and invoice dates. Review and book those drafts in Fiken; this does not email them to customers. Older local drafts are not sent automatically just because they are still drafts. If delivery cannot be confirmed, DealJourney keeps the attempt for verification instead of creating another draft. Check Fiken before retrying, and ask support to reconcile an unresolved attempt. A booked invoice cannot be changed by resyncing its former draft.

Products on an invoice line. When an invoice goes out to the accounting system, each line has to point at a product over there. DealJourney matches yours to theirs by product code first, then by name. When nothing matches, it sends the line without a product link and writes the miss to the sync log, so you can create the product in the accounting system yourself and keep control of the account and VAT code it uses. Turn on the create-missing-products setting only if you would rather it made them for you. Leaving it off is the safer default: a product invented per line, per push, is how an accounting product list fills up with duplicates of the same thing.

Invoices you have started but not sent. An invoice that is still being prepared in the accounting system is a different thing from one that has gone out, and by default only sent invoices are reflected in the CRM. For PowerOffice Go you can also show the unsent ones, using Visa oskickade PowerOffice-fakturor i fakturalistan on the integration's settings page. They appear in the invoice list as drafts, so a salesperson can see that a sale is already queued in the accounting system before sending it a second time, and they disappear from the list again as soon as PowerOffice turns one into a real invoice. It is off until you switch it on, because it adds rows to a page that is otherwise only sent invoices.

Projects and hours with PowerOffice Go. Four switches on the integration's settings page decide how far this goes, and invoicing itself stays in PowerOffice. Bringing projects in and sending them out are separate choices, so you can have either without the other.

• Hämta projekt från PowerOffice: projects come in with their number, status and what has been invoiced so far. Archived projects come in too, already archived, and stay out of the project list and the project pickers. Tick Visa arkiverade on the project list to browse them, or search by name, which finds them either way.
• Skapa projekt i PowerOffice när en affär vinns: När en affär markeras som vunnen skapas ett projekt för den i PowerOffice. Finns det redan ett projekt med samma projektkod kopplas det i stället.
• Skicka projekt som skapats i DealJourney till PowerOffice: projects made in DealJourney appear in PowerOffice, and renaming or closing one here follows it there. They are created as billed by the hour, so hourly work never turns into a fixed price by accident. Bara projekt som skapas efter att du slår på detta skickas.
• Synka timmar och frånvaro med PowerOffice: Timmar och frånvaro som registreras i DealJourney skickas till PowerOffice, och timmar som registreras i PowerOffice visas här. Timmar som redan fakturerats i PowerOffice låses. How that looks on the timesheet: Log hours.