Scoped
The entities, mailboxes, workflows and ERP integration named in the statement of work.
Implementation & support
Live in 45 days, supported by the team that built the product and implements your ERP.
Stream implementations follow one methodology: discover the process, configure the platform, integrate the ERP, test real scenarios, train the people, cut over, then stay engaged. The 45-day contract-to-go-live guarantee applies to every scoped implementation.
45-day go-live guaranteeERP implementers on the projectManaged support after go-live
Methodology
Six stages from contract to go-live
Each stage has defined inputs, outputs and owners. Most customers reach go-live in less than the guaranteed 45 days.
- 1Discovery (days 1–7)
Map intake channels, invoice types, PO mix, entities, dimensions, approval policy, exceptions and posting rules. Confirm ERP records and integration identity. Output: configuration and integration design.
- 2Configuration (days 5–20)
Entities, mailboxes, capture rules, coding defaults, duplicate and matching tolerances, approval workflows, expense policy and procurement approvals configured from the design.
- 3ERP integration (days 8–25)
Connect the non-production ERP, synchronize master data, configure posting policy per entity, validate dimension combinations and periods.
- 4Testing (days 20–35)
Representative invoices, POs, receipts and expense reports through capture, coding, matching, approval, posting, error and retry scenarios. Sign-off against the design.
- 5Training (days 28–40)
Role-based sessions for AP, approvers, buyers, controllers and administrators, with guides and short videos for the approver experience.
- 6Cutover and hypercare (days 38–45)
Production integration, mailbox switch, open-invoice load, daily check-ins for the first two weeks, then transition to support.
The 45-day guarantee
What the guarantee means, precisely
We put it in the agreement because the implementation model is repeatable: the same people configure the product and integrate the ERP.
Measured
45 calendar days from contract signature to production go-live with trained users.
Backed
If Skalable misses the date for reasons within its control, the remedy in the agreement applies.
Dependent on
Timely ERP access, an integration identity, sample documents and decision-makers available for working sessions.
Expandable
Additional entities, Expense Management, Procurement or new integrations are added under their own scoped plans.
Track record
Documented customers went live and scaled from 40+ to 300+ locations and to 600 invoices a week on Dynamics 365.
Support model
What happens after go-live
Support is provided by the team that builds Stream and implements the ERPs it posts into, not a separate help desk reading a script.
Named support contact
A person who knows your configuration and integration.
Response targets
Ticket severity levels with response and update targets defined in your agreement; phone escalation for production issues.
Monitoring
Integration heartbeats, mailbox health and posting failures monitored, with alerts to your AP lead.
Releases
Regular releases with customer-visible notes; changes affecting your configuration reviewed with you first.
Managed services
Optional ongoing capacity for enhancements, new entities, workflow changes, reporting and integration operations.
Adoption reviews
Quarterly reviews of automation rates, bottlenecks and configuration opportunities.
Questions
Implementation and support FAQs
What exactly does the 45-day guarantee cover?
A scoped implementation, agreed in the statement of work, goes live within 45 calendar days of contract signature: the entities, mailboxes, workflows and ERP integration named in the scope, with your users trained. If Skalable misses the date for reasons within its control, the remedy defined in the agreement applies. Additional entities, modules or integrations added later follow their own scoped plans.
What do we need to provide?
A project owner, access to the ERP environment and an integration identity, sample invoices and your approval policy, and availability for two to three working sessions a week during configuration and testing.
Do you migrate historical invoices?
Open invoices in flight are typically loaded at cutover. Historical documents can be imported for search and duplicate detection where useful; scope is agreed in discovery.
How is the ERP integration tested?
In a non-production ERP environment with representative invoices, POs, receipts and expense reports, covering matching, posting, error and retry scenarios, before production cutover.
What does support look like after go-live?
A named support contact, a ticketing channel with response targets, monitoring of integrations and mailboxes, release notes for every update, and managed-service options for enhancements, new entities and integration operations.
Next step
Plan your implementation
Tell us your ERP, entities and target date. We will come back with a scoped plan and the go-live date we will guarantee.