A salesperson calls a customer with a new offer, not knowing the company has three invoices overdue. An accountant sets up a customer that sales won a week ago \u2014 by hand, with a typo in the company ID. Both situations have the same cause: the CRM and the ERP are two separate worlds. This article shows what to sync between Raynet and your ERP, the three ways to connect them, and where these projects get stuck in practice.<\/p>\n
Let the CRM own the address book and the ERP own documents and the price list \u2014 and let invoices with payments flow automatically into Raynet while new companies and won deals flow into the ERP.<\/strong> Raynet has a public REST API, so you can connect it with an off-the-shelf connector, a custom script or an integration platform. You need a platform as soon as you want two-way traffic with matching by company ID and errors that report themselves<\/strong> \u2014 typically the moment your sales process starts depending on CRM data.<\/p>\n<\/div>\n The point of the integration is not to \u201csync everything\u201d but to give each person the data they work with. In practice, four areas get synced:<\/p>\n Raynet is a Czech cloud CRM and a grateful integration partner: it has a public, documented REST API<\/strong> \u2014 you generate access as an API key right in your instance settings, with no waiting for the vendor and no paid add-on module. The bottleneck is usually the ERP side: Money S4\/S5<\/a> offer modern APIs, Money S3<\/strong> opens up via XML data exchange and POHODA<\/strong> via mServer<\/a>, which only ships with certain editions. The ERP therefore always dictates the architecture \u2014 Raynet adapts.<\/p>\n Ready-made connectors exist for the most common pairs \u2014 you will find them in Raynet\u2019s integration catalogue and from specialised vendors. Deployment takes days, you pay a monthly fee, and the standard scenario works out of the box. The limit is the same as with every boxed solution: the mapping is fixed<\/strong>. It transfers what the connector was built for; the moment you want your own matching rules, want to filter which companies belong in the ERP, or need to sync the custom fields you tailored Raynet with, you hit the wall.<\/p>\n Raynet\u2019s API on one side, the ERP\u2019s XML or API on the other \u2014 and a capable developer wires them together. Functionally that works, and for one-way transfers it is often the fastest route. The hidden cost is maintenance: the script has to handle request rate limits, retries on outages, structure changes after ERP updates and logging so an error can be traced at all. Above all, it has an author \u2014 and authors leave. A company integration only one person understands is a risk, not a solution.<\/p>\n A platform has connectors for both Raynet and the ERP ready-made, and the build consists of configuring the mapping: what gets matched by company ID, when the CRM wins and when accounting does, which statuses get synced. Transfers run in a queue with automatic retries, every record can be traced in a log, and errors arrive as notifications \u2014 not as a phone call from a salesperson. With a third system (e-commerce, warehouse, Outlook) the difference grows: it plugs into the same hub instead of adding yet another standalone bridge. When each architecture pays off is covered in detail in our article on integration platforms<\/a>.<\/p>\n Most often we connect Raynet with Money S3<\/a> \u2014 typically invoices with payments into the CRM and new companies the other way \u2014 and Raynet with POHODA<\/a>, where editions and mServer come into play. The same logic applies to any CRM though: for example Zoho CRM with Money S5<\/a>. For the view from the other side \u2014 what POHODA can do with various CRMs \u2014 see our separate guide<\/a>; all supported pairs are in the integration catalogue<\/a>.<\/p>\n The most tempting brief \u2014 \u201cjust sync the address book both ways\u201d \u2014 is also the most common source of trouble. A salesperson creates a company in the CRM, an accountant creates the same company in the ERP, each slightly differently, and the sync dutifully spreads both versions into both systems. The fix is to create records in one direction, match by company ID and have conflicts reported instead of silently overwritten.<\/p>\n<\/div>\n We know Raynet up close \u2014 we build our own product for syncing Raynet with Outlook<\/a> on its API, so we know how it behaves in daily traffic, not just in the docs. We build ERP integrations per data area (usually 6\u201312 hours of work per area), running with a queue, a log and 24\/7 monitoring. What we can sync with Raynet is on the Raynet detail page<\/a>; the pricing page with an online calculator<\/a> estimates the cost of your combination.<\/p>\n Yes \u2014 a public, documented REST API. Access works via an API key you generate in your own instance settings, so the integration depends neither on the vendor nor on a paid module. The API is exactly how Raynet connects to ERPs, email and other tools.<\/p>\n<\/details>\n An off-the-shelf connector runs from tens of euros a month. A platform integration is priced per data area \u2014 the build usually takes 6\u201312 hours of work per area, plus a monthly fee for operation. The online calculator<\/a> gives a concrete number for your pair.<\/p>\n<\/details>\n Because invoices are created in the ERP and without an integration that is where they stay. The fix is an automatic sync of invoices and their payments onto the company card in the CRM \u2014 sales then sees revenue, receivables and payment history without begging accounting for data.<\/p>\n<\/details>\n Companies are matched by registration number (contacts by email), records are created in one clearly defined direction, and a conflict \u2014 say two different addresses for the same company \u2014 gets reported instead of one version silently overwriting the other.<\/p>\n<\/details>\nWhat to sync between CRM and ERP<\/h2>\n
\n
What Raynet offers to the outside<\/h2>\n
Path 1: An off-the-shelf connector<\/h2>\n
Path 2: A custom script over the API<\/h2>\n
Path 3: An integration platform<\/h2>\n
\n
The most common pairs in practice<\/h2>\n
What to check before going live<\/h2>\n
\n
Trap: a two-way address book without rules manufactures duplicates<\/h2>\n
How we do it at Symmy<\/h2>\n
Frequently asked questions<\/h2>\n
Does Raynet have an API?<\/summary>\n
How much does connecting Raynet to Money S3 or POHODA cost?<\/summary>\n
Why can\u2019t sales see invoices in the CRM?<\/summary>\n
What does a well-configured address book sync look like?<\/summary>\n