Contract lifecycle runs in your ERP. Stamping can too.
Your customers already generate HR, procurement, and vendor contracts in your ERP. Stamping shouldn't be the one compliance step that sends them to MyTax. Partner API handles employment and loan submissions; web app covers the rest — so the whole surface is answered.
What changes for your customers
What changes for your customers
Employment, loan, tenancy, general contracts — all stamped, all retrievable alongside the source.
One less "you'll need to also do X on MyTax" slide in the rollout deck.
The customer's ops team doesn't get pulled into MyTax for post-submission follow-ups.
What changes for your business
HR, procurement, vendor, legal — stamping covered across the ERP.
Commission per the partnership agreement on every customer that signs up through your referral.
Your teams stop fielding "what about stamping" mid-rollout.
The things that go away
The "MyTax for stamping" sentence in your implementation documentation.
Customer churn on renewals where compliance is the stated reason.
Workarounds your customers built with spreadsheets and manual MyTax logins.
Under the hood
For your engineering and implementation teams.
POST /api/integration/employment/submit
POST /api/integration/loan/submit
ContractConfirmed, ContractProcessing, ContractCompleted, ContractFailed
Stamp through the Kenal web app under the document types system today. API coverage expanding.
Integration, answered.
Employment and loan today. Tenancy and general contracts stamp through the web app.
Yes. Each type has its own endpoint; your orchestration stays on your side.
Yes. Each customer has their own workspace, wallet, and certificates.
Handled offline by our team. The customer is only contacted when we need their input.
Referral code at signup. Commission percentage and duration per your partnership agreement.