Kraya solutions
A connected process. Clear places to start.
You may need help with one part of purchasing or several handovers across the business. Explore the modules by the work your team needs to do. The grouping below is for navigation, not a set of compulsory product bundles.
Explore each solution
Source & order
- Vendor onboardingGet vendor details ready for review.
- Master dataStart with organised procurement records.
- Indents & requestsGive every requirement a clear starting point.
- RFQ & comparativeMake the quotes comparable.
- PO & approvalsKeep the decision with the order.
- AuctionsBring competitive bidding into sourcing.
Move & receive
- Post-PO & ASNKeep the work moving after the PO.
- Parking & gateBring gate activity into the purchase record.
- Inventory & issuanceConnect material requirements with stock-related work.
- Transport & fleetBring transport into the operational picture.
- Distributor managementInclude distributor operations in the wider workflow.
Check & control
- Goods receiptKeep what arrived with what was ordered.
- Quality controlKeep quality checks with the receipt.
- Invoice automationCheck the invoice in its purchase context.
- Vendor paymentsKeep payment status with the purchase.
- Spend analyticsSee spend in a clearer context.
- BudgetingKeep planned spend in the buying conversation.
Choose and approve
Vendor onboarding and management
Collect supplier details and prepare them for buyer review.
Let the vendor fill the details. Let your team review them.
From repeated requests to a supplier profile.
A purchase should not begin with someone retyping vendor details from documents and emails. Suppliers enter the information requested for their profile in Kraya.
Check the information coming in.
GST, PAN and MSME checks run on the details submitted. Follow-ups help bring missing information back into the process, so the buyer can review the profile.
Keep approval with the buyer.
Submitting a profile is not the same as being approved. The buying team reviews the supplier before proceeding under its own process.
See a supplier profile take shape. Follow a vendor submission through checks, missing-information follow-up and buyer review.
See vendor onboardingPurchase requests and indenting
Bring the requirement into the purchase process.
A purchase starts with a need. Keep that need in view.
Give the requirement a clear starting point.
Bring the purchase request or indent into the purchasing process instead of leaving it as a disconnected message.
Carry the requirement into sourcing.
Use the request as the starting point for the quotation and ordering workflow. The team can discuss the requirement before it becomes an order.
Match the route to the organisation.
Review how requests should move between locations, departments and approvers. The exact fields and routing are agreed for the process being implemented.
Start with a request from your team. Follow it into sourcing and review the approval handovers it needs.
Explore purchase requestsRFQs and quote comparison
Review offers before selecting a supplier.
A lower quote is only the start of the comparison.
Ask suppliers against the requirement.
Create an RFQ and bring supplier responses into the sourcing process. Give the buying team a defined point from which to compare offers.
Compare before choosing.
Review quotations side by side rather than jumping between separate messages and sheets. Discuss the rates and terms relevant to the purchase before selecting the offer.
Take the choice into the order.
Move the selected quotation through the approval and PO process. A comparison supports the buyer decision; it does not replace it.
Bring two quotes you need to compare. See how the buying team can review the offers and move its choice towards an order.
See quote comparisonPurchase orders and approvals
Carry the decision into an approved order.
An approved order should carry an informed decision.
From selection to order.
Carry the selected quotation into the purchase-order process so ordering follows the sourcing decision.
Send the decision to the right people.
Configure approvals by location and department. Add an escalation matrix at the stages that need it, rather than assuming one approval chain fits every purchase.
Agree the ERP handover.
Decide which order activities happen in Kraya and which remain in the ERP. Data exchange and the division of work depend on the interfaces available in your setup.
Map an approval that often gets stuck. Review the locations, departments and escalation steps involved in that decision.
Explore PO approvalsReceive and check
ASN: Advance shipping notice
Share dispatch details against the order.
Know what is being sent before it arrives.
Make dispatch part of the purchase.
Suppliers share dispatch information against the purchase order through the ASN process.
Prepare the receiving handover.
Bring invoice, e-way bill, vehicle and driver details into the dispatch handover. Review the documents and approval sequence required for your own deliveries.
Continue into gate and receipt.
Use the dispatch information as part of the handover to gate and receiving teams. An ASN is notice of dispatch, not proof that goods were received or accepted.
Follow a dispatch into receiving. See how an ASN prepares the information for the next delivery handover.
See the ASN workflowTransport management
Include transport in the purchase workflow.
The purchase does not stop when the supplier dispatches.
Include the movement between order and receipt.
Transport is part of the purchase handover, not an unrelated activity. Review it alongside dispatch, gate entry and receiving.
Start with the movement you run.
Show us how transport is arranged and which teams need the movement information. The demo should reflect that process rather than assume every business operates its own fleet.
Define the scope before implementation.
See the transport workflow in context, from the dispatch handover to the receiving team. Agree the functions and interfaces needed for your setup.
Bring your transport process to the discussion. Walk through dispatch, movement information and the handover at your receiving site.
Discuss transport managementGate management
Connect vehicle entry and gate inwards with receiving.
What enters the gate should not lose the order behind it.
Bring the vehicle into the receiving process.
Record the vehicle-entry stage and the information needed for the delivery handover.
Keep gate inwards connected.
Use PO verification and a vehicle entry/exit slip as part of the gate-inwards process. Review the gate checks and responsibilities required at your sites.
Pass the delivery to the receiving team.
Continue the information into goods receipt and quality review, with the checks and responsibilities mapped to your site.
Walk through one delivery at your gate. Review what the gate team records, checks and passes to stores.
See gate managementGoods receipt: GRN
Record the receiving stage against the purchase.
An order says what was expected. A receipt says what arrived.
Record the receiving stage.
Bring the GRN into the purchase workflow so the receiving record can support the next checks.
Keep receipt and acceptance distinct.
Physical receipt and quality acceptance are different decisions. Map how stores and quality teams record and review them in your process.
Give invoice review its receiving record.
Three-way matching uses the PO, GRN and invoice. Agree how goods receipt and quality checks fit with the ERP and the invoice-review process.
Follow what arrived into invoice review. See where the receipt record fits with the order, quality check and invoice.
Explore goods receiptQuality control
Enter batch-wise details and test results before invoice recording moves ahead.
Received is not the same as accepted.
Put quality into the handover.
Kraya places a dedicated QC module between GRN and invoice recording.
Capture the results behind the decision.
The quality team can enter batch-wise details and submit test results. Keep that review visible before the invoice moves ahead.
Map the checks your material needs.
Discuss your tests, sign-offs and exceptions during the demo. Map the quality review to the materials and processes your team handles.
Bring a material and its quality checks. Walk through batch details, test results and the sign-offs your team needs.
See quality controlMatch and prepare payment
Invoice automation and three-way matching
Compare the PO, GRN and invoice; review differences.
What was ordered. What arrived. What was billed.
Bring the invoice into the purchase record.
Move invoice work into a process that has the order and receiving information available for checking.
Make the comparison explicit.
Three-way matching compares the PO, GRN and invoice. Rate or quantity differences can be brought forward for review instead of being treated as automatically acceptable.
Keep exceptions with the people who decide.
The accounts team reviews differences and the required next steps under the agreed process, before the invoice moves to its next stage.
Bring an invoice that did not match. Compare it with the order and receipt, then review how the difference should be handled.
See three-way matchingPayment tracking and readiness
Follow the payment-related status after invoice review.
Keep the payment follow-up connected to the purchase.
Do not lose the invoice after checking it.
Payment follow-up is part of the wider purchase cycle. Review the payment-related status and handover alongside invoice matching.
Know what the next team needs.
Discuss the checks and information your finance team requires before it treats an invoice as ready for payment.
Agree the handover to finance.
Map the handover to the ERP, accounting system or bank process your team uses. Define the steps that belong in Kraya and the steps handled outside it.
Map the steps after invoice review. Identify the information finance needs and the payment-status handovers your team wants to track.
Discuss payment trackingSee across the whole process
Configurable approvals and ERP interfaces support the workflow across modules. Integration scope depends on available interfaces and access.
Spend analytics, reports and dashboards
Bring purchasing information into management review, with reports tailored to the measures you need.
See the purchase work as a business picture.
Step back from individual transactions.
Use reports and dashboards to review purchasing information across the process rather than looking at one order or invoice in isolation.
Ask the questions your team works with.
Alongside the default reports, custom spend analysis can focus on the KPIs relevant to your workflow and management review.
Build decisions on the available data.
Agree the data sources, report definitions and reporting scope, so the team knows what each view represents.
Bring the report your team asks for every month. Review the data and measures it needs, and discuss the right reporting scope.
Explore spend reportingMore modules
Vendors and master data
Master data management
Review the master data your purchasing process needs. Bring your item and vendor records to the demo so the team can explain the relevant scope.
Stores
Inventory management and issuance
Review your stock and material-issue requirements with the Kraya team. Use your stores process to check the module's fit and scope.
Finance
Budgeting
Discuss how your team plans and reviews purchase spending. Ask the Kraya team to show the budgeting module against your requirements.
Purchasing
Auctions
Invite suppliers to bid in a reverse auction for selected purchases. Your team reviews the bids and decides the award.
Wider operations
Distributor management
Discuss how your distributor network works. Ask the Kraya team to explain the module's fit for your operating process.
Keep development plans separate from available software.
Vaarta, WhatsApp-based workflows and decision intelligence are in development. Open tenders is a separate direction being explored.
Start with the handover that needs fixing.
Tell us which team is waiting on which information. We will use that process to shape the demo.