{"id":72086,"date":"2026-08-27T15:00:00","date_gmt":"2026-08-27T13:00:00","guid":{"rendered":"https:\/\/symmy.com\/erpedie\/propojeni-raynetu-s-erp\/"},"modified":"2026-08-27T15:00:00","modified_gmt":"2026-08-27T13:00:00","slug":"propojeni-raynetu-s-erp","status":"publish","type":"erpedie","link":"https:\/\/symmy.com\/cs\/erpedie\/propojeni-raynetu-s-erp\/","title":{"rendered":"Propojen\u00ed Raynetu s ERP: Money S3, POHODA a co si pohl\u00eddat"},"content":{"rendered":"<p>Obchodn\u00edk vol\u00e1 z\u00e1kazn\u00edkovi s novou nab\u00eddkou a nev\u00ed, \u017ee mu firma dlu\u017e\u00ed t\u0159i faktury po splatnosti. \u00da\u010detn\u00ed zakl\u00e1d\u00e1 odb\u011bratele, kter\u00e9ho obchod z\u00edskal p\u0159ed t\u00fddnem \u2014 ru\u010dn\u011b a s p\u0159eklepem v I\u010cO. Ob\u011b situace maj\u00ed stejnou p\u0159\u00ed\u010dinu: CRM a ERP jsou dva odd\u011blen\u00e9 sv\u011bty. Tenhle \u010dl\u00e1nek ukazuje, co mezi Raynetem a ERP p\u0159en\u00e1\u0161et, jak\u00e9 t\u0159i cesty propojen\u00ed existuj\u00ed a na \u010dem podobn\u00e9 projekty v praxi zadrh\u00e1vaj\u00ed.<\/p>\n<h2>Kr\u00e1tk\u00e1 odpov\u011b\u010f<\/h2>\n<div class=\"ep-answer\">\n<p><strong>Adres\u00e1\u0159 a\u0165 vede CRM, doklady a cen\u00edk ERP \u2014 a mezi nimi a\u0165 automaticky te\u010dou faktury s \u00fahradami do Raynetu a nov\u00e9 firmy se zak\u00e1zkami do ERP.<\/strong> Raynet m\u00e1 ve\u0159ejn\u00e9 REST API, tak\u017ee propojit ho jde hotov\u00fdm konektorem, vlastn\u00edm skriptem i integra\u010dn\u00ed platformou. <strong>Platformu pot\u0159ebujete, jakmile chcete obousm\u011brn\u00fd provoz s p\u00e1rov\u00e1n\u00edm podle I\u010cO a chybami, kter\u00e9 se ohl\u00e1s\u00ed samy<\/strong> \u2014 tedy typicky ve chv\u00edli, kdy na datech v CRM za\u010dne st\u00e1t obchod.<\/p>\n<\/div>\n<h2>Co mezi CRM a ERP p\u0159en\u00e1\u0161et<\/h2>\n<p>Smysl propojen\u00ed nen\u00ed \u201esynchronizovat v\u0161echno&#8220;, ale dostat ke ka\u017ed\u00e9mu \u010dlov\u011bku data, se kter\u00fdmi pracuje. V praxi se p\u0159en\u00e1\u0161ej\u00ed \u010dty\u0159i agendy:<\/p>\n<ul class=\"ep-cards\">\n<li><strong>Firmy a kontakty<\/strong>Obchodn\u00edk zalo\u017e\u00ed firmu v Raynetu, v ERP vznikne odb\u011bratel s\u00e1m \u2014 se spr\u00e1vn\u00fdm I\u010cO, adresou z rejst\u0159\u00edku a bez p\u0159episov\u00e1n\u00ed.<\/li>\n<li><strong>Faktury a \u00fahrady<\/strong>Doklady se vystavuj\u00ed v ERP; u firmy v Raynetu vid\u00ed obchod odb\u011bry, otev\u0159en\u00e9 pohled\u00e1vky a platebn\u00ed mor\u00e1lku d\u0159\u00edv, ne\u017e zvedne telefon.<\/li>\n<li><strong>Zak\u00e1zky a obchodn\u00ed p\u0159\u00edpady<\/strong>Vyhran\u00fd obchodn\u00ed p\u0159\u00edpad v CRM se prom\u011bn\u00ed v zak\u00e1zku \u010di objedn\u00e1vku v ERP \u2014 bez e-mailu \u201epros\u00edm zalo\u017e&#8220;.<\/li>\n<li><strong>Produkty a cen\u00edky<\/strong>P\u00e1nem cen\u00edku je ERP; Raynet nab\u00edz\u00ed do nab\u00eddek aktu\u00e1ln\u00ed polo\u017eky a ceny, ne kopii z lo\u0148ska.<\/li>\n<\/ul>\n<h2>Co Raynet um\u00ed navenek<\/h2>\n<p>Raynet je \u010desk\u00fd cloudov\u00fd CRM a pro integrace je to vd\u011b\u010dn\u00fd partner: m\u00e1 <strong>ve\u0159ejn\u00e9, dokumentovan\u00e9 REST API<\/strong> \u2014 p\u0159\u00edstup si vygenerujete jako API kl\u00ed\u010d p\u0159\u00edmo v nastaven\u00ed sv\u00e9 instance, \u017e\u00e1dn\u00e9 \u010dek\u00e1n\u00ed na v\u00fdrobce ani p\u0159\u00edplatkov\u00fd modul. U\u017e\u0161\u00ed hrdlo b\u00fdv\u00e1 strana ERP: <a href=\"\/cs\/aplikace\/money-s4\/\">Money S4\/S5<\/a> nab\u00edzej\u00ed modern\u00ed API, <strong>Money S3<\/strong> se otev\u00edr\u00e1 p\u0159es XML v\u00fdm\u011bnu dat a <strong>POHODA<\/strong> p\u0159es <a href=\"\/cs\/erpedie\/pohoda-mserver\/\">mServer<\/a>, kter\u00fd je jen v n\u011bkter\u00fdch edic\u00edch. Architekturu propojen\u00ed proto v\u017edy ur\u010duje ERP \u2014 Raynet se p\u0159izp\u016fsob\u00ed.<\/p>\n<h2>Cesta 1: Hotov\u00fd konektor<\/h2>\n<p>Pro nejb\u011b\u017en\u011bj\u0161\u00ed dvojice existuj\u00ed hotov\u00e9 konektory \u2014 najdete je v katalogu integrac\u00ed Raynetu i u specializovan\u00fdch firem. Nasazen\u00ed je ot\u00e1zka dn\u016f, plat\u00ed se m\u011bs\u00ed\u010dn\u00ed poplatek a standardn\u00ed sc\u00e9n\u00e1\u0159 funguje z krabice. Limit je stejn\u00fd jako u v\u0161ech krabicov\u00fdch \u0159e\u0161en\u00ed: <strong>mapov\u00e1n\u00ed je pevn\u00e9<\/strong>. P\u0159en\u00e1\u0161\u00ed se to, s \u010d\u00edm konektor po\u010d\u00edt\u00e1; jakmile chcete vlastn\u00ed pravidla p\u00e1rov\u00e1n\u00ed, filtrovat, kter\u00e9 firmy do ERP pat\u0159\u00ed, nebo p\u0159en\u00e1\u0161et vlastn\u00ed pole, kter\u00fdmi jste si Raynet p\u0159izp\u016fsobili, naraz\u00edte.<\/p>\n<h2>Cesta 2: Vlastn\u00ed skript p\u0159es API<\/h2>\n<p>Raynet API na jedn\u00e9 stran\u011b, XML nebo API ERP na druh\u00e9 \u2014 a \u0161ikovn\u00fd v\u00fdvoj\u00e1\u0159 je spoj\u00ed. Funk\u010dn\u011b to nen\u00ed probl\u00e9m a pro jednosm\u011brn\u00fd p\u0159enos to b\u00fdv\u00e1 nejrychlej\u0161\u00ed cesta. Skryt\u00e1 cena je \u00fadr\u017eba: skript mus\u00ed \u0159e\u0161it limity po\u010dtu po\u017eadavk\u016f, opakov\u00e1n\u00ed p\u0159i v\u00fdpadku, zm\u011bny struktur po aktualizaci ERP a logov\u00e1n\u00ed, a\u0165 se d\u00e1 chyba v\u016fbec dohledat. A hlavn\u011b m\u00e1 autora \u2014 a auto\u0159i odch\u00e1zej\u00ed. Firemn\u00ed integrace, o kter\u00e9 v\u00ed jeden \u010dlov\u011bk, je riziko, ne \u0159e\u0161en\u00ed.<\/p>\n<h2>Cesta 3: Integra\u010dn\u00ed platforma<\/h2>\n<p>Platforma m\u00e1 konektor pro Raynet i pro ERP hotov\u00fd a stavba spo\u010d\u00edv\u00e1 v nastaven\u00ed mapov\u00e1n\u00ed: co se p\u00e1ruje podle I\u010cO, kdy m\u00e1 p\u0159ednost CRM a kdy \u00fa\u010detnictv\u00ed, kter\u00e9 stavy se p\u0159en\u00e1\u0161ej\u00ed. P\u0159enosy b\u011b\u017e\u00ed ve front\u011b s automatick\u00fdm opakov\u00e1n\u00edm, ka\u017ed\u00fd z\u00e1znam se d\u00e1 dohledat v logu a o chyb\u011b p\u0159ijde notifikace \u2014 ne telefon\u00e1t od obchodn\u00edka. S t\u0159et\u00edm syst\u00e9mem (e-shop, sklad, Outlook) se rozd\u00edl je\u0161t\u011b zv\u011bt\u0161\u00ed: p\u0159ipoj\u00ed se do stejn\u00e9ho st\u0159edu, m\u00edsto aby vedle sebe vznikaly dal\u0161\u00ed samostatn\u00e9 m\u016fstky. Kdy se kter\u00e1 architektura vyplat\u00ed, rozeb\u00edr\u00e1 <a href=\"\/cs\/erpedie\/co-je-integracni-platforma\/\">\u010dl\u00e1nek o integra\u010dn\u00edch platform\u00e1ch<\/a>.<\/p>\n<ul class=\"ep-cards\">\n<li><strong>Konektor<\/strong>Pevn\u00fd sc\u00e9n\u00e1\u0159 z krabice. Nasazen\u00ed ve dnech, m\u011bs\u00ed\u010dn\u00ed poplatek, mapov\u00e1n\u00ed neohnete.<\/li>\n<li><strong>Platforma<\/strong>Mapov\u00e1n\u00ed na m\u00edru: p\u00e1rov\u00e1n\u00ed podle I\u010cO, vlastn\u00ed pole, filtry. Stavba po agend\u00e1ch, cena podle rozsahu.<\/li>\n<li><strong>Vlastn\u00ed skript<\/strong>Rychl\u00fd start, ale \u00fadr\u017eba, limity API a odchod autora jsou va\u0161e riziko.<\/li>\n<li><strong>Platforma<\/strong>Fronta s opakov\u00e1n\u00edm, log ka\u017ed\u00e9ho z\u00e1znamu a notifikace p\u0159i chyb\u011b \u2014 provoz se hl\u00edd\u00e1 s\u00e1m.<\/li>\n<\/ul>\n<h2>Nej\u010dast\u011bj\u0161\u00ed dvojice v praxi<\/h2>\n<p>Nej\u010dast\u011bji propojujeme <a href=\"\/cs\/integrace\/raynet-money-s3\/\">Raynet s Money S3<\/a> \u2014 typicky faktury s \u00fahradami do CRM a nov\u00e9 firmy opa\u010dn\u00fdm sm\u011brem \u2014 a <a href=\"\/cs\/integrace\/raynet-pohoda-komplet\/\">Raynet s POHODOU<\/a>, kde se nav\u00edc \u0159e\u0161\u00ed edice a mServer. Stejn\u00e1 logika ale plat\u00ed pro jak\u00e9koli CRM: t\u0159eba <a href=\"\/cs\/integrace\/zoho-crm-money-s5\/\">Zoho CRM s Money S5<\/a>. Pokud v\u00e1s zaj\u00edm\u00e1 pohled z druh\u00e9 strany \u2014 co dok\u00e1\u017ee POHODA s r\u016fzn\u00fdmi CRM \u2014 m\u00e1me k tomu <a href=\"\/cs\/erpedie\/propojeni-pohody-s-crm\/\">samostatn\u00fd pr\u016fvodce<\/a>; v\u0161echny podporovan\u00e9 dvojice najdete v <a href=\"\/cs\/systemy-integrace\/\">katalogu integrac\u00ed<\/a>.<\/p>\n<h2>Co si pohl\u00eddat p\u0159ed spu\u0161t\u011bn\u00edm<\/h2>\n<ol class=\"ep-steps\">\n<li><strong>Jeden p\u00e1n pro ka\u017edou agendu.<\/strong> Adres\u00e1\u0159 vede CRM, doklady a cen\u00edk ERP. Kdy\u017e stejn\u00e9 pole edituje oboj\u00ed bez pravidel, vyhraje ten, kdo synchronizoval pozd\u011bji \u2014 a to nen\u00ed pravidlo, to je loterie.<\/li>\n<li><strong>P\u00e1rov\u00e1n\u00ed podle I\u010cO, ne podle n\u00e1zvu.<\/strong> \u201eACME s.r.o.&#8220; a \u201eACME, s. r. o.&#8220; jsou pro \u010dlov\u011bka jedna firma, pro syst\u00e9m dv\u011b. I\u010cO je jedin\u00fd spolehliv\u00fd kl\u00ed\u010d; u kontakt\u016f e-mail.<\/li>\n<li><strong>\u00dahrady, ne jen faktury.<\/strong> Platebn\u00ed mor\u00e1lku d\u011blaj\u00ed \u00fahrady a splatnosti. P\u0159enos, kter\u00fd skon\u010d\u00ed u vystaven\u00fdch faktur, \u0159ekne obchodn\u00edkovi kolik fakturujete \u2014 ne kdo neplat\u00ed.<\/li>\n<li><strong>Prvn\u00ed migrace historie.<\/strong> Ne\u017e pote\u010de denn\u00ed provoz, mus\u00ed se jednor\u00e1zov\u011b sp\u00e1rovat st\u00e1vaj\u00edc\u00ed firmy a doplnit historie doklad\u016f. Je to samostatn\u00fd krok projektu \u2014 kdo ho p\u0159esko\u010d\u00ed, p\u00e1ruje duplicity za provozu.<\/li>\n<li><strong>Co se stane p\u0159i chyb\u011b.<\/strong> Firma bez I\u010cO, v\u00fdpadek ERP, doklad, kter\u00fd neprojde validac\u00ed. Spr\u00e1vn\u00e1 odpov\u011b\u010f obsahuje frontu, automatick\u00e9 opakov\u00e1n\u00ed, notifikaci a log \u2014 \u201epo\u0161leme to znovu ru\u010dn\u011b&#8220; spr\u00e1vn\u00e1 odpov\u011b\u010f nen\u00ed.<\/li>\n<\/ol>\n<div class=\"ep-note\">\n<h2>Past: obousm\u011brn\u00fd adres\u00e1\u0159 bez pravidel vyr\u00e1b\u00ed duplicity<\/h2>\n<p>Nejl\u00e1kav\u011bj\u0161\u00ed zad\u00e1n\u00ed \u2014 \u201ea\u0165 se adres\u00e1\u0159 synchronizuje ob\u011bma sm\u011bry&#8220; \u2014 je z\u00e1rove\u0148 nej\u010dast\u011bj\u0161\u00ed zdroj probl\u00e9m\u016f. Obchodn\u00edk zalo\u017e\u00ed firmu v CRM, \u00fa\u010detn\u00ed tut\u00e9\u017e firmu v ERP, ka\u017ed\u00fd trochu jinak, a synchronizace poctiv\u011b roznese ob\u011b verze do obou syst\u00e9m\u016f. \u0158e\u0161en\u00ed je nastavit zakl\u00e1d\u00e1n\u00ed jedn\u00edm sm\u011brem, p\u00e1rovat podle I\u010cO a konflikty nechat hl\u00e1sit, ne ti\u0161e p\u0159episovat.<\/p>\n<\/div>\n<h2>Jak to d\u011bl\u00e1me v Symmy<\/h2>\n<p>Raynet zn\u00e1me zbl\u00edzka \u2014 na jeho API stav\u00edme i vlastn\u00ed produkt pro <a href=\"\/cs\/integrace\/raynet-outlook\/\">synchronizaci Raynetu s Outlookem<\/a>, tak\u017ee v\u00edme, jak se chov\u00e1 v ka\u017edodenn\u00edm provozu, ne jen v dokumentaci. Propojen\u00ed s ERP stav\u00edme po agend\u00e1ch (obvykle 6\u201312 hodin pr\u00e1ce na agendu), b\u011b\u017e\u00ed s frontou, logem a dohledem 24\/7. Co v\u0161echno um\u00edme s Raynetem p\u0159en\u00e1\u0161et, najdete na <a href=\"\/cs\/aplikace\/raynet\/\">detailu Raynetu<\/a>; orienta\u010dn\u00ed cenu va\u0161\u00ed kombinace spo\u010d\u00edt\u00e1 <a href=\"\/cs\/kalkulacka\/\">cen\u00edk s online kalkula\u010dkou<\/a>.<\/p>\n<h2>\u010cast\u00e9 ot\u00e1zky<\/h2>\n<details class=\"ep-faq\">\n<summary>M\u00e1 Raynet API?<\/summary>\n<p>Ano \u2014 ve\u0159ejn\u00e9 REST API s dokumentac\u00ed. P\u0159\u00edstup funguje p\u0159es API kl\u00ed\u010d, kter\u00fd si vygenerujete v nastaven\u00ed vlastn\u00ed instance, tak\u017ee integrace nez\u00e1vis\u00ed na v\u00fdrobci ani na p\u0159\u00edplatkov\u00e9m modulu. Pr\u00e1v\u011b p\u0159es API se Raynet propojuje s ERP, e-maily i dal\u0161\u00edmi n\u00e1stroji.<\/p>\n<\/details>\n<details class=\"ep-faq\">\n<summary>Kolik stoj\u00ed propojen\u00ed Raynetu s Money S3 nebo POHODOU?<\/summary>\n<p>Hotov\u00fd konektor vyjde na stokoruny a\u017e ni\u017e\u0161\u00ed tis\u00edce m\u011bs\u00ed\u010dn\u011b. Integrace na platform\u011b se po\u010d\u00edt\u00e1 po agend\u00e1ch \u2014 stavba obvykle 6\u201312 hodin pr\u00e1ce na agendu a k tomu m\u011bs\u00ed\u010dn\u00ed provoz. Konkr\u00e9tn\u00ed \u010d\u00edslo pro va\u0161i dvojici spo\u010d\u00edt\u00e1 <a href=\"\/cs\/kalkulacka\/\">online kalkula\u010dka<\/a>.<\/p>\n<\/details>\n<details class=\"ep-faq\">\n<summary>Pro\u010d obchodn\u00edk v CRM nevid\u00ed faktury?<\/summary>\n<p>Proto\u017ee faktury vznikaj\u00ed v ERP a bez propojen\u00ed tam i z\u016fstanou. \u0158e\u0161en\u00edm je automatick\u00fd p\u0159enos faktur a jejich \u00fahrad k firm\u011b do CRM \u2014 obchodn\u00edk pak u z\u00e1kazn\u00edka vid\u00ed odb\u011bry, pohled\u00e1vky a platebn\u00ed mor\u00e1lku, ani\u017e by se dopro\u0161oval \u00fa\u010dt\u00e1rny.<\/p>\n<\/details>\n<details class=\"ep-faq\">\n<summary>Jak se pozn\u00e1 dob\u0159e nastaven\u00e1 synchronizace adres\u00e1\u0159e?<\/summary>\n<p>Firmy se p\u00e1ruj\u00ed podle I\u010cO (kontakty podle e-mailu), zakl\u00e1d\u00e1n\u00ed jede jedn\u00edm jasn\u011b ur\u010den\u00fdm sm\u011brem a konflikt \u2014 t\u0159eba dv\u011b r\u016fzn\u00e9 adresy u t\u00e9\u017ee firmy \u2014 se ohl\u00e1s\u00ed, m\u00edsto aby jedna verze ti\u0161e p\u0159epsala druhou.<\/p>\n<\/details>\n<details class=\"ep-faq\">\n<summary>Jde k dat\u016fm kolem Raynetu pustit AI?<\/summary>\n<p>Nejp\u0159\u00edm\u011bj\u0161\u00ed dnes dostupn\u00e1 cesta vede p\u0159es ERP: <a href=\"\/cs\/erp-mcp\/\">MCP servery Symmy<\/a> zp\u0159\u00edstup\u0148uj\u00ed AI asistent\u016fm data \u00fa\u010detn\u00edch syst\u00e9m\u016f \u2014 a s propojen\u00fdm CRM se do ERP dostanou i obchodn\u00ed data, na kter\u00e1 se pak AI um\u00ed pt\u00e1t. Samotn\u00fd Raynet m\u00e1 otev\u0159en\u00e9 API, tak\u017ee je na napojen\u00ed AI n\u00e1stroj\u016f dob\u0159e p\u0159ipraven\u00fd.<\/p>\n<\/details>\n","protected":false},"excerpt":{"rendered":"<p>Pro\u010d obchodn\u00edk v CRM nevid\u00ed faktury a platebn\u00ed mor\u00e1lku? Co mezi Raynetem a ERP p\u0159en\u00e1\u0161et, t\u0159i cesty propojen\u00ed \u2014 hotov\u00fd konektor, vlastn\u00ed skript p\u0159es API, integra\u010dn\u00ed platforma \u2014 a pasti, kter\u00e9 se uk\u00e1\u017eou a\u017e za provozu.<\/p>\n","protected":false},"author":0,"featured_media":72087,"template":"","erpedie-topic":[102],"class_list":["post-72086","erpedie","type-erpedie","status-publish","has-post-thumbnail","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/symmy.com\/cs\/wp-json\/wp\/v2\/erpedie\/72086","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/symmy.com\/cs\/wp-json\/wp\/v2\/erpedie"}],"about":[{"href":"https:\/\/symmy.com\/cs\/wp-json\/wp\/v2\/types\/erpedie"}],"version-history":[{"count":0,"href":"https:\/\/symmy.com\/cs\/wp-json\/wp\/v2\/erpedie\/72086\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/symmy.com\/cs\/wp-json\/wp\/v2\/media\/72087"}],"wp:attachment":[{"href":"https:\/\/symmy.com\/cs\/wp-json\/wp\/v2\/media?parent=72086"}],"wp:term":[{"taxonomy":"erpedie-topic","embeddable":true,"href":"https:\/\/symmy.com\/cs\/wp-json\/wp\/v2\/erpedie-topic?post=72086"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}