SYSTEM // LOADING
BIDQUEST // 2026
GRID // 1280px
BIDQUEST // 2026
Zero manual search • 100% Free
Separate tender fees, processing charges and EMD, verify payment instructions, and build a payment register that prevents avoidable submission errors.

A business may download the tender documents without charge and still face a fee elsewhere in the process. Alternatively, the tender may have no document fee but require bid security. Read the payment provisions rather than inferring costs from the download experience.
The practical objective is simple: every required payment should have a verified instruction, an owner, a deadline and a matching record in the final bid.

| Category | Question to resolve | Internal record |
|---|---|---|
| Tender or document fee | What charge is stated for this procurement? | Amount, recipient, payment reference |
| Processing or portal charge | Is a separate service or processing payment required? | Current instruction and receipt |
| EMD or bid security | What bid-stage security or approved alternative applies? | Instrument, payment or exemption evidence |
Descriptions vary between procuring systems. Use the names appearing in the actual notice, then determine their meaning from the accompanying conditions. Avoid classifying an unfamiliar charge simply because it resembles a payment in an earlier tender.
The official Rajasthan portal, for example, separately references bid document fees, bid security and RISL processing fees in its notices. That establishes why separate checks matter, but does not establish a current universal fee or payment route. Official reference.

Verify instructions from the official tender record. A payment request forwarded by a consultant, salesperson or unofficial chat should not be the sole basis for transferring funds.
Record the beneficiary, account or portal channel, tender reference, permitted payment method and any stated cut-off. Have another person compare sensitive beneficiary details with the original instructions when an external transfer is required.
If the documents conflict, raise a clarification through the permitted route. Do not resolve the conflict by choosing whichever instruction makes payment easiest.
Payment initiation and confirmed payment are different events. Your coordinator should establish which evidence the portal or buyer requires and confirm that it is available before declaring the payment row complete.

If a business expects relief, specify which requirement it concerns. A certificate relevant to EMD does not automatically answer whether a document fee or processing charge is waived.
Maintain a short claim record: benefit requested, relevant policy or tender clause, business category, supporting evidence and unresolved questions. Selecting an exemption option should follow this review.
Do not upload a certificate and assume the buyer will work out every possible benefit. Follow the prescribed claim process and attach the requested evidence in the right place.
Where applicability remains unclear, keep the status unresolved and obtain the appropriate clarification. An optimistic interpretation is not an approved exemption.

A charge paid for participation and a deposit that may be released later affect the business differently. Ask finance to determine the appropriate accounting treatment for each actual payment.
For bid planning, use separate columns for cash paid, money temporarily unavailable, expected release conditions and direct expenses. Track instrument charges and financing costs where relevant.
This prevents two opposite mistakes: treating every rupee as permanently lost, or removing a refundable deposit entirely from the cash plan. Money that is expected back later is still unavailable until it is returned.
Assume an illustrative tender states a ₹2,000 document fee, a ₹1,000 processing charge and a ₹1 lakh EMD. These are example values, not prescribed charges.
Without an applicable exemption, the immediate funding requirement is ₹1,03,000, before bank or transaction costs. Finance should separately review the ₹3,000 charges and the ₹1 lakh security treatment.
If an EMD exemption is confirmed, do not automatically reduce the other two rows to zero. Record the basis for each waived amount. If only EMD is waived, the example's remaining charges total ₹3,000.
Now suppose accounts sends the correct ₹1 lakh but uses a reference belonging to another bid. The issue is not affordability; it is reconciliation. The payment register should expose that mismatch before submission.
Accounts should send the coordinator the required receipt or instrument information through an approved internal channel. The coordinator compares it with the tender requirement and updates the checklist.
Check amount, tender identity, payer identity where relevant, beneficiary, date, instrument validity and submission method. Do not assume an image cropped to show the amount contains every required detail.
Keep the final evidence file readable. If physical originals are required by the specific tender, assign their delivery separately and retain proof. An online scan should not conceal an unmet original-document condition.
Create an internal deadline ahead of the official cutoff. Allow time for confirmation, document preparation and any prescribed reconciliation step.
If a transaction fails or its status is uncertain, check the official payment status and support route before repeating it. A duplicate transfer can create a new refund problem without resolving the first transaction.
Record the incident and tell the bid owner whether submission readiness has been affected. Do not mark a row complete merely because money appears debited in a bank message.
Use a four-question check: have all required payment rows been identified; are paid amounts reconciled; are claimed exemptions supported; and is the required evidence in the final file set?
After submission, retain the acknowledgement and payment record together. For security release, hand the record to the person responsible for follow-up. For paid charges, preserve the accounting trail.
Divide the work into preparation, authorization and reconciliation. The preparer extracts the amount and instructions. The authorised finance person approves or executes the payment. The coordinator confirms the required evidence belongs to the correct event.
One employee may perform more than one role in a small business, but the three checks should remain visible. A transfer made from a correct bank account can still reference the wrong tender. A correct tender receipt can still be uploaded in the wrong slot.
Use a payment request containing the official reference, purpose, amount, deadline and source. Include the relevant instruction, not a cropped image showing only beneficiary details. That lets the approver understand why payment is needed.
After execution, record the bank reference and official payment status as separate fields. If the system requires another confirmation, keep that step open until it is complete.
Suppose accounts receives a request for three payments but the bid coordinator expects an exemption on one. Do not let the disagreement become a last-minute argument over the total.
Compare the applicable exemption row with the exact payment category. Establish whether the available certificate supports the claim and whether the formal response or tender provides the required route. Have the bid owner decide any remaining uncertainty with the appropriate review.
If relief is confirmed only for security, prepare that claim and process the remaining required charges. If treatment is unresolved, record the consequence for affordability and submission readiness.
The final register should explain the decision. It should not contain a blank amount that forces the uploader to guess whether it means zero, waived, pending or forgotten.
Consider a hypothetical business preparing four opportunities. Each has ₹75,000 of bid security and ₹2,500 of participation charges, under the example's assumed conditions.
Together, the immediate payment requirement is ₹3.10 lakh: ₹3 lakh in security and ₹10,000 in charges. Finance must also consider any instrument costs, overlapping award requirements and operating commitments.
The point is not that the four tenders are expensive. It is that reviewing each independently can conceal peak exposure. Mark expected payment and release dates on one calendar and ask which releases are confirmed rather than anticipated.
If the business expects an exemption on two bids, model both the supported claim case and the consequence if that claim is not accepted. Do not describe the lower figure as certain while applicability is unresolved.
Name internal receipt files with a short tender identity, purpose and date. The filename should make sense without containing unnecessary bank details. Retain the original receipt inside the controlled folder.
Store an index linking the payment request, approval, transaction, official receipt and submitted file. That gives finance a traceable path without forcing everyone to access the entire banking record.
When an employee leaves or the task changes hands, transfer the register and official references. A deposit tracked only in one person's messages can become difficult to follow up later.
If a correction is made, retain what changed and why. Do not replace the record silently so the next reviewer cannot tell which version was uploaded.
Suggested internal statuses are identified, approved, initiated, confirmed, evidence prepared, submitted and reconciled. For a supported exemption, use claim reviewed and claim submitted rather than payment completed.
These labels are internal controls, not official portal statuses. Keep the actual system wording alongside them where relevant.
The coordinator should escalate a row that is initiated but unconfirmed before the internal cutoff. Finance should investigate a bank debit without matching evidence. The bid owner should see which remaining task could prevent a compliant offer.
A useful management review is therefore short: what must be paid, what has been confirmed, what claim is supported, and what remains unresolved. That is more actionable than a single green “fees done” cell.
For a straightforward payment, a small register and second check can be sufficient. Do not create a large approval bureaucracy for every minor charge.
Increase review when instructions conflict, the recipient changed, the security is substantial or the team proposes an exemption. Focus effort where a mistake would affect cash or qualification.
The purpose is a reliable bid, not paperwork volume. Each retained field should explain a requirement, a decision or an outstanding action.
No. Check the actual payment conditions and submission instructions.
Do not assume so. Review each category separately.
Only if the current procurement specifies it. Systems and instructions can differ.
First establish transaction status through the official channel and your bank. Avoid creating duplicates through guesswork.
The record required by the actual procurement, reconciled with the correct tender and amount.
Add three separate payment rows to your next bid checklist and assign accounts and coordination owners. Explore BidQuest for tender discovery, then verify all payment and exemption requirements against the issuing authority's record.
www.eproc.rajasthan.gov.in. Accessed 12 Oct 2026.

Learn how to read government tender documents in India: NIT, eligibility, technical specifications, BOQ, EMD, evaluation, corrigenda and submission checklist.
Read the guide
Learn how Indian MSMEs and contractors can find government tenders on CPPP, GeM and state portals, shortlist relevant notices and track corrigenda.
Read the guide
Provisional accounts are acceptable only if the applicable tender requirements permit them on the relevant basis.
Read the guide