ERP — Unternehmensmanagement
Omie-MCP
Specialists für Omie: Finanzen und Treasury, Vertrieb und CRM, Einkauf, Lager und Fertigung, Services und Verträge, Steuern und E-Rechnung, Buchhaltung, APIs und Integrationen, Onboarding.
Specialists
Sie müssen den Specialist nicht selbst auswählen: Der Manager Agent leitet jede Frage an den weiter, der das Thema abdeckt. Öffnen Sie eine Karte, um zu sehen, wann er zum Einsatz kommt und was außerhalb seines Bereichs liegt.
Dieser Inhalt ist auf Englisch verfügbar.
Funktionaler Kern
Finance & Treasury Specialist
Specialist in Omie's Finance module: accounts payable and receivable, bank accounts, categories, cash flow, bank reconciliation, bank collection, CNAB, boletos (bank slips), Pix and Omie.CASH.
- Accounts Payable & Receivable
- Bank Accounts, Transfers & Cash
- Bank Reconciliation
- Bank Collection
- Omie.CASH
Details anzeigen
Einsatz für
- Accounts payable and receivable: creating, editing, settling/paying off, partial settlement, cancellation and item status
- Bank accounts, balances, transfers between accounts and cash
- Financial categories and departments/cost centers applied to financial entries
- Cash flow, revenue and expense forecasts originating from orders, work orders and contracts
- Bank reconciliation: importing OFX statements, reconciling entries and discrepancies
- Bank collection: portfolios, per-bank configuration, boleto, collection Pix, Bolecode
- Payments via CNAB remittance and return file import, payment approval
- Omie.CASH (integrated digital account): collections, paying boletos/bills/taxes, receipts
- Interest, fines, discounts, surcharges, advances and pass-throughs in accounts payable/receivable
- Financial operations via the financas/contapagar, financas/contareceber and financas/contacorrente API services
Nicht abgedeckt
- Doesn't define taxation rules, CST/CSOSN or withholdings on tax documents, or handle NF-e/NFS-e rejections (refer to the Tax and Electronic Documents Specialist)
- Doesn't handle generating accounting files, SPED, chart of accounts or accounting layouts (refer to the Accounting and Accountant Dashboard Specialist)
- Doesn't answer for authentication, usage limits, webhooks or integration architecture (refer to the APIs and Integrations Specialist)
- Doesn't give legal or accounting opinions on legal obligations
- Doesn't claim a banking method, integrated bank or Omie.CASH feature is available without confirmation in the Omie Help Center
Funktionaler Kern
Sales, CRM & Billing Specialist
Specialist in customer and supplier records, CRM (opportunities, process stages, pipeline, ticket/proposal), sales orders and quotes, product invoicing, returns, price lists, salespeople and commissions.
- Customer & Supplier Records
- CRM
- Sales Ticket/Proposal
- Quotes & Sales Orders
- Price Lists & Payment Terms
- Salespeople & Commissions
Details anzeigen
Einsatz für
- Customer, supplier, carrier and contact records (geral/clientes service)
- CRM: opportunities, process stages, temperature, sales pipeline, opportunities dashboard, pipeline reports
- Sales ticket/proposal: products, services, recurring services, amounts and period
- Quotes and sales orders: stages, approval, stock reservation and availability, invoicing
- Sales returns, order cancellation and invoicing reversal in the sales flow
- Price lists, payment terms, order installments (lista_parcelas), discounts and freight
- Salespeople, teams, partners, projects and commission calculation
- Order integration with Finance (revenue forecast) and Inventory (issue/reservation)
- The produtos/pedido (IncluirPedido, ConsultarPedido) and crm/oportunidades (UpsertOportunidade, ListarOportunidades) APIs from a business-functional standpoint
Nicht abgedeckt
- Doesn't define item tax configuration or analyze NF-e/NFC-e rejections (refer to the Tax and Electronic Documents Specialist)
- Doesn't handle work orders, recurring service contracts or NFS-e (refer to the Services, Work Orders and Contracts Specialist)
- Doesn't handle average cost, stock counts, warehouses or production (refer to the Purchasing, Inventory and Production Specialist)
- Doesn't answer for marketplace/e-commerce order integration through Omie.Hub (refer to the Platforms and Ecosystem Specialist)
- Doesn't presume a field, order stage or CRM feature exists without confirmation in the official documentation
Funktionaler Kern
Purchasing, Inventory & Production Specialist
Specialist in the Purchasing, Inventory and Production module: purchase requisitions and orders, inbound invoices, product records, stock movements and adjustments, stock locations, stock counts, costs and production orders with product structure.
- Inbound Invoices & Supplier NF-e
- Products, Families & Variations
- Stock Movements
- Stock Locations & Warehouses
- Stock Counts & Discrepancies
- Inventory Costs & Average Cost
Details anzeigen
Einsatz für
- Purchase requisition, quote, purchase order, approval and conversion into an inbound entry
- Inbound invoices and importing supplier NF-e (goods receipt and its effect on inventory/finance)
- Product and family records, characteristics, units, variations and kits
- Stock movements: receipts, issues, adjustments, manual and per-period movements
- Stock locations/warehouses, consolidated balances, stock summary and position
- Stock counts, bulk quantity updates and checking discrepancies
- Inventory costs, CMC (average cost) and manual cost adjustments
- Lot and expiry control (manufacturing/expiration dates) in purchasing, production and sales processes
- Production orders (OP), product structure/BOM, input consumption and production orders generated from a sales order
- APIs for products, inventory (adjustments, lookup, movements, locations), purchase orders, inbound invoices, structure and production orders
Nicht abgedeckt
- Doesn't define CFOP, CST/CSOSN, NCM or tax calculation for the operation (refer to the Tax and Electronic Documents Specialist)
- Doesn't handle the financial side of payables generated by the purchase (refer to the Finance and Treasury Specialist)
- Doesn't handle the sales process, CRM or sales invoicing (refer to the Sales, CRM and Invoicing Specialist)
- Doesn't handle services, work orders or recurring contracts (refer to the Services, Work Orders and Contracts Specialist)
- Doesn't recommend changing balances or costs through direct database access; only official screens and APIs
Funktionaler Kern
Services, Work Orders & Contracts Specialist
Specialist in Omie's Services and NFS-e module: service records, work orders, recurring service contracts, individual and batch invoicing, and day-to-day issuance of the service invoice (NFS-e).
- Work Orders
- Service Contracts
- Products Used in Services
- Service Reports
- servicos/os APIs
Details anzeigen
Einsatz für
- Service records, municipal service codes and the service's financial data
- Work orders: opening, stages, services and products used, completion and cancellation
- Service contracts: term, recurrence (monthly, quarterly etc.), price adjustment, suspension and cancellation
- Invoicing work orders and contracts, individually and in batches, and billing forecasts
- Generating and viewing the service invoice from a work order/contract and its effect on accounts receivable
- Products specified in the service/contract and their effect on inventory
- Service reports: work orders by billing forecast, contracts and recurrence
- The servicos/os APIs (IncluirOS, invoicing and batch invoicing) and servicos/contrato (contracts and invoicing), including fields such as nCodServico and nQtde
Nicht abgedeckt
- Doesn't define ISS rules, withholdings or service CST/tax classification, or analyze NFS-e rejections (refer to the Tax and Electronic Documents Specialist)
- Doesn't handle product sales orders or goods NF-e (refer to the Sales, CRM and Invoicing Specialist)
- Doesn't handle bank collection or reconciliation of the generated items (refer to the Finance and Treasury Specialist)
- Doesn't presume integration with a city hall or availability of a municipal layout without official confirmation
- Doesn't invent undocumented work order/contract methods, parameters or statuses
Steuern & Compliance
Tax & e-Documents Specialist
Specialist in electronic tax documents and tax configuration in Omie: NF-e, NFC-e, NFS-e, CFOP, NCM, CST, CSOSN, taxes and withholdings, XML/DANFE, SEFAZ rejections and Tax Reform adjustments (IBS/CBS).
- SEFAZ Rejections
- Tax Configuration
- Service Taxation
- Tax Reform
- Recipient Acknowledgment & Inbound Invoices
- Tax Regimes
Details anzeigen
Einsatz für
- Issuing, canceling, correction letters/corrections and voiding number ranges for NF-e and NFC-e in Omie
- Interpreting and handling SEFAZ rejections (e.g. 527, 567, 600, 1024) and document status
- Tax configuration: CFOP, NCM, CEST, CST/CSOSN, origin, ICMS, ICMS-ST, IPI, PIS/COFINS, DIFAL
- Service taxation: ISS, withholdings (IRRF, INSS, PIS/COFINS/CSLL) and municipal NFS-e rules
- Tax Reform: configuring IBS and CBS, tax classification, the mandatory adoption timeline and impacts on the XML
- Tax XML, DANFE/DANFE NFC-e, access key, protocol, resending and document storage
- Recipient acknowledgment (manifestação do destinatário) and tax consistency of inbound invoices
- Tax regimes (Simples Nacional, Lucro Presumido/Real) and their effect on invoice configuration
Nicht abgedeckt
- Doesn't replace the opinion of the responsible accountant or decide the customer's tax classification
- Doesn't handle generating accounting/SPED files or integration with the accounting system (refer to the Accounting and Accountant Dashboard Specialist)
- Doesn't handle the operational cycle of orders, work orders or inventory (refer to the corresponding functional experts)
- Doesn't answer for API authentication and consumption (refer to the APIs and Integrations Specialist)
- Doesn't state that a tax rule is in effect without checking official sources (nfe.fazenda.gov.br, gov.br, planalto.gov.br, Omie Help Center)
Steuern & Compliance
Accounting & Accountant Portal Specialist
Specialist in Omie's Accountant Dashboard and accounting integration: chart of accounts, accounting system layouts, mapping categories and cost centers, generating accounting and tax files, ancillary obligations and management accounting reports.
- Accountant Dashboard Setup
- Accounting & Management Reports
- Accountant Access & Monthly Close
- OneFlow for Accounting
Details anzeigen
Einsatz für
- Accountant Dashboard checklist and setup steps (layout, chart of accounts, mappings, file generation)
- Importing the chart of accounts, reading record 0500 from a SPED file and the SPED referential chart
- Accounting system layouts and automatic integrations with third-party accounting software
- Mapping financial categories and cost centers/departments to the chart of accounts
- Generating accounting and tax files per period, checking and reprocessing them
- Accounting and management reports (income statement, calculations, statements available in the ERP)
- The accountant's role in accessing the customer's environment and the monthly closing routine
- The OneFlow platform in the accounting context (standard chart of accounts and accounting firm operations)
Nicht abgedeckt
- Doesn't issue formal accounting opinions or sign off obligations; supports the licensed professional
- Doesn't configure tax document taxes or interpret rejections (refer to the Tax and Electronic Documents Specialist)
- Doesn't handle day-to-day settlements, reconciliation or collection (refer to the Finance and Treasury Specialist)
- Doesn't claim compatibility with a specific accounting layout without confirmation in the Omie Help Center
- Doesn't recommend extracting accounting data through direct database access
Technische Plattform
APIs & Integrations Specialist
Technical Specialist in the Omie APIs and integration architecture: Developer Portal, SOAP/JSON services at app.omie.com.br/api/v1, app_key/app_secret authentication, Bearer tokens for the newer APIs, pagination, usage limits, error handling and webhooks.
- Developer Portal & API List
- Authentication
- Usage Limits
- Error Handling
- Pagination
- Idempotency & Integration Codes
Details anzeigen
Einsatz für
- Developer Portal and API list: finding the service, method, parameters and version
- Calling services at app.omie.com.br/api/v1/<module>/<resource>/ with POST and a JSON body (call, app_key, app_secret, param)
- Authentication: obtaining the Access Key (App Key/App Secret), differences between legacy APIs and Bearer-token APIs (e.g. OneFlow), secure credential storage
- Usage limits: 960 req/min per IP, 240 req/min per IP+App Key+Method, 4 concurrent requests, Too Many Requests and the 30-minute HTTP 425 block
- Error handling: SOAP faultstring, record already registered for an integration code, nonexistent lookup code, PROTO_BYEBYE and safe reprocessing
- Pagination (page, records per page, total pages) and initial vs. incremental load strategies by last-modified date/time
- Idempotency and traceability with integration codes (e.g. codigo_produto_integracao, codigo_pedido_integracao)
- Omie webhooks: receiving endpoint, enabling events in the app, consuming and reprocessing notifications
- Consuming data in external tools (API queries in Excel and Power BI with pagination), testing with SoapUI and inspecting the WSDL
- APIs that support technical administration, such as user management via API, and official integration best practices
Nicht abgedeckt
- Doesn't invent endpoints, methods, JSON fields, webhook events or error codes not documented in the Developer Portal or the Help Center
- Doesn't recommend direct access to Omie's internal database or reverse engineering of screens
- Doesn't expose App Keys, App Secrets, tokens or passwords; uses fictitious examples only
- Doesn't decide a module's functional business rules (refer to the corresponding functional expert)
- Doesn't presume that credentials and authentication flows of different APIs are interchangeable
Technische Plattform
Platforms & Ecosystem Specialist
Specialist in the complementary platforms of the Omie ecosystem: Omie.Store (app store), Omie.Hub (marketplaces and e-commerce), Omie.PDV, the Omie mobile app and the Omie Portal/Shopping Cart.
- Omie.Store
- Omie.Hub
- Omie.PDV / Retail
- Omie App
- Omie Portal & Shopping Cart
- App Activation for Specific Offers
Details anzeigen
Einsatz für
- Omie.Store: app catalog, activation, purchasing and plan dependencies
- Omie.Hub: publishing listings, stock control per channel, capturing and managing marketplace and e-commerce orders
- Mapping channel orders to sales orders in the ERP and handling discrepancies
- Omie.PDV / retail: point-of-sale operation and POS-specific permissions
- Omie App (Android/iOS), including mobile CRM and restricting app access
- Omie Portal and Shopping Cart: configuration and use by the end customer
- Distinguishing native features, Store apps and third-party integrations
- Activating apps for customers on specific offers (e.g. Omie.Hub via Omie.Store)
Nicht abgedeckt
- Doesn't replace the third-party app vendor's documentation or guarantee its behavior
- Doesn't detail API contracts or authentication for custom integrations (refer to the APIs and Integrations Specialist)
- Doesn't define tax rules for captured orders (refer to the Tax and Electronic Documents Specialist)
- Doesn't handle the internal sales cycle of the order or CRM (refer to the Sales, CRM and Invoicing Specialist)
- Doesn't claim a channel, marketplace or app is available without confirming on Omie.Store/the Help Center
Governance & Betrieb
Administration & Onboarding Specialist
Specialist in Omie environment administration and implementation: access groups and user profiles, access security (2FA, IPs, schedules), general settings and company parameters, implementation checklists per module and guides per industry segment.
- Access Security
- Implementation Checklists by Module
- Incident Triage
- Preparing for Integrations
Details anzeigen
Einsatz für
- Access groups, fixed and custom profiles, permissions per module and per feature
- Access security: two-factor authentication, allowed IPs, access hours, environment access control
- General settings and company parameters, issuer data, series and numbering, multiple companies
- Implementation checklists per module (Finance; Sales and NF-e; Purchasing, Inventory and Production; Accountant Dashboard) and getting-started guides per segment (retail, manufacturing, services)
- Implementation sequencing, initial master data load and post-go-live validation
- Omie's monthly release notes and updates as a source of behavior changes
- Incident triage: telling apart a functional failure, a permission restriction, a contract/plan limitation and a service outage
- Preparing the environment for integrations (integration user/app and required permissions)
Nicht abgedeckt
- Doesn't negotiate or confirm commercial terms, prices or the scope of a purchased plan
- Doesn't resolve module-specific business rules (refer to the corresponding functional expert)
- Doesn't define API contracts or debug integrations (refer to the APIs and Integrations Specialist)
- Doesn't change configuration in a production environment without validation from the account owner and those responsible
- Doesn't claim a permission, parameter or profile exists without confirmation in the Omie Help Center