Integrations
Connect AMODIT with the systems your teams already use. Move data between workflows and business applications through integrations designed around each process.
ERP, Finance & Registries
ERP & Business Applications
AMODIT exchanges workflow data with ERP and other business applications. Delivered connections include SAP, Symfonia, Comarch ERP XL and Comarch ERP Optima, enova365, Microsoft Dynamics, Exact, and TETA. Each workflow defines its own scope, such as reference data, documents, and return statuses.
KSeF Connector
KSeF Connector sends sales invoices to and retrieves purchase invoices from KSeF (Poland’s National e-Invoicing System). It connects AMODIT or other business software with Poland’s e-invoicing service. Designed for organizations operating in Poland.
Payment Batch
AMODIT generates a file containing selected domestic or international transfers in specified currencies. Finance teams import the batch into their banking system for processing.
VIES
AMODIT retrieves VAT number validation results from the VAT Information Exchange System (VIES) during document processing. The validation result appears directly in the workflow.
Rejestr.io
AMODIT retrieves company data from Rejestr.io and uses it to populate workflow forms. The integration supports checks of records from Poland’s National Court Register (KRS), including legal status, board members, shareholders, and representation rules. For organizations operating in Poland.
Polish VAT Whitelist (Biała lista)
AMODIT checks a supplier’s VAT status and bank account against the Polish VAT Whitelist (Biała lista). The integration also returns information about registration denials, removals, and reinstatements. For organizations operating in Poland.
National Bank of Poland (NBP) Exchange Rates
AMODIT retrieves current exchange rates from the National Bank of Poland (NBP) for use in invoices and financial workflows. For organizations operating in Poland.
OCR & Data Capture
Symfonia OCR
Symfonia OCR extracts data from invoice images and converts it into structured digital data for use in AMODIT workflows.
ABBYY FlexiCapture
ABBYY FlexiCapture extracts selected data from invoices, contracts, shipping documents, and other forms. AMODIT can use the captured data to populate workflow forms and continue document processing.
Signatures & TrustCenter
AMODIT TrustCenter
AMODIT TrustCenter supports electronic signing of documents with partners, subcontractors, contractors, employees, and managers. Signing takes place within the document workflow.
Qualified Electronic Signatures
Qualified electronic signatures can be used in AMODIT and AMODIT TrustCenter on Windows devices. For cloud-based signing across devices, AMODIT integrates with SimplySign.
SimplySign with TrustCenter
The SimplySign integration brings cloud-based qualified electronic signatures into AMODIT TrustCenter. Users sign documents directly through the cloud service in TrustCenter.
e-dowód with TrustCenter
AMODIT TrustCenter can use Poland’s e-dowód functionality to verify identity and support an electronic signature based on the Polish e-ID card. For organizations operating in Poland.
Identity & Access
Active Directory
Active Directory integration creates AMODIT user accounts from existing directory accounts. Administrators manage access according to the organization’s established policies and procedures.
Microsoft Entra ID
Microsoft Entra ID integration, formerly Azure Active Directory (Azure AD), supports identity and access management for AMODIT in cloud and on-premises environments. It enables single sign-on and access based on assigned roles and permissions.
OAuth (Google, Facebook, Microsoft), OpenID, SAML
Users can sign in to AMODIT with existing external accounts through OAuth providers such as Google, Facebook, and Microsoft, or through OpenID and SAML.
Correspondence & Shipping
eDoręczenia
AMODIT connects eDoręczenia (Poland’s electronic registered mail service) with incoming and outgoing correspondence workflows. Electronic messages and acknowledgments of receipt join mail and email in one correspondence process. For organizations operating in Poland.
eNadawca
AMODIT sends recipient and shipment data from documents to eNadawca, the Poczta Polska shipping platform, and generates labels for letters, parcels, and pallets. For organizations operating in Poland.
FedEx
AMODIT registers shipping orders in FedEx from workflow data. Users can follow shipment status in AMODIT and respond when delivery issues arise.
DHL
DHL integration uses AMODIT workflow data to generate shipping labels and track parcels. Employees handle shipment preparation and status checks within the workflow.
HR & Notifications
eRecruiter
AMODIT extends eRecruiter workflows with additional process steps. Candidate data can support tasks such as preparing and electronically signing documents with candidates.
SMS API
AMODIT sends SMS messages from within a workflow. Teams can use them to deliver important process information to selected recipients.
Collaboration & Documents
SharePoint
AMODIT integrates with SharePoint to store and share documents outside the workflow platform. Documents can move through creation, completion, approval, and archiving while teams retain their established SharePoint workspace.
Microsoft 365
Teams can create, edit, and comment on Microsoft 365 documents together, then move those documents into an AMODIT workflow for review or approval.
Google Workspace
AMODIT integrates with Gmail for sending and receiving documents, Google Drive for cloud storage, and Google Docs for real-time collaboration. Teams pass documents from these services into AMODIT workflows for further processing.
AMODIT exchanges data through SQL views, SOAP and REST APIs, flat files, and data buses. The integration method is selected for the connected system and workflow.
Finance integrations work in both directions. Supplier, account, cost centre and project dictionaries can feed AMODIT; approved invoices and accounting allocations move to the finance system; posting or payment status can return to the workflow.
Data supplied through SQL or an API can be combined with workflow data in a shared Advanced Reports view.
What actually moves between systems
Data direction is part of the integration design. Source data can feed an AMODIT workflow, approved results can move out, and return information can update the case.
Master data into AMODIT
Source systems can provide employee or supplier records, organization structures, and reference lists such as accounts, cost centres, projects, and other form values.
Documents, metadata, and attachments
AMODIT can receive documents with descriptive data and attachments. After the workflow steps are complete, a document can move to a signing service, finance system, or another business application.
Accounting data and return information
After approval, AMODIT can send the document and accounting allocation. Posting, payment, synchronization, signing, or rejection status can return to the case together with a signed file where the process requires it.
Validation, rejection, and retry
Error handling and retries are a standard part of an integration. Acceptance rules, messages, and retry behaviour are defined for the interface involved.
1. Define validation for the interface
Each interface defines the required data scope and format. Validation rules follow the connected systems rather than a universal rule set shared by every integration.
2. Return an acceptance or rejection status
Where the interface provides feedback, the receiving system can confirm acceptance or return a rejection status with information needed for correction.
3. Correct and retry
Once the data is corrected, the exchange runs again. The next result updates the workflow status according to the design of that connection.
Choose the method around the connected system
No single method fits every environment. The available interface, data direction, exchange frequency, and deployment model determine the appropriate approach.
REST API or SOAP
Use a web service when the connected system exposes operations for forms, documents, tasks, or statuses. The available interfaces on both sides define the operations in scope.
SQL views and staging tables
Use database access when the agreed exchange can read from views or work through staging tables. This pattern can carry reference lists, descriptive data, and statuses.
SFTP, XML, and Excel
Use file exchange when a system imports or exports a defined format. SFTP transfers the files, while XML or Excel provides the agreed data structure.
Google Sheets and Cloud Agent
Google Sheets can provide and receive spreadsheet data. Cloud Agent retrieves files from a resource inside the organization’s environment when the workflow needs to bring them into AMODIT.
Tell us which systems and data flows you want to connect. We will discuss an integration approach for your workflow.
Optimize Key Areas
Finance
Automate financial workflows and reduce errors resulting from manual tasks.
Human Resources
Store all employee data in one place and simplify HR tasks through automation.
Legal
Optimize the work of your legal department – organize contracts and addenda in a single system, granting your team easy access to vital information.
Administration
Reduce delays, avoid errors, and eliminate lost documents by automating administrative workflows.
IT
Enhance projects monitoring and management for your IT team with an efficient, automated system.