Build a Payment Due Tracker for Verified Receipts and Remaining Balances

1. Gather these details

• Choose a fictional agreement with a total and known instalments. Use a short project reference rather than customer identity details or bank account numbers.
• Record dates and amounts actually agreed. If a date remains undecided, mark it for agreement instead of inventing a deadline that could misrepresent the arrangement.
• Choose one currency for the first example. Do not combine different currencies into one balance; currency conversion requires separate decisions outside this simple project.
• Define how you verify money outside the tool, such as checking your own account. A customer’s message stays unconfirmed until you complete that step.
• Choose short receipt references that let you find your evidence without copying bank screenshots or card details into the register. Record what you checked and when.

2. Define how the project works

1. Record the agreement and its instalments

Start with the agreed total and currency, then enter each instalment’s amount, due date and reference. Instalments should add up to the total, or the difference should be displayed for you to resolve. The tool must not silently redistribute a discrepancy because that could change the agreement. Record the reason and date of later schedule changes while retaining the customer’s agreement separately in your normal correspondence.

2. Separate a payment report from a receipt

When a customer says they paid, record reported payment or awaiting verification without reducing the confirmed balance. Check your account through your usual method, then enter the verified amount, receipt date and short reference. A message or screenshot can help locate a transaction but is not automatic verification. Never ask for a customer’s password or one-time code to complete this process or update your register. Assign each receipt entry to one instalment so it reduces that instalment’s balance only.

3. Handle partial payments and corrections

Record only the amount actually received when an instalment is partly paid. Keep separate receipt entries so their dates remain understandable. Correct mistaken entries with a reason instead of adding imaginary opposite transactions. Flag a receipt total above the agreement for review: the extra amount might belong to another project or result from duplication. Do not automatically increase the contract total merely to make the numbers appear consistent.

4. Review overdue amounts against a visible date

Show the date used by the report and allow a selected review date for testing. An unpaid instalment becomes overdue after its due date; an amount due today belongs in a separate category. Review remaining amounts and follow up yourself according to the agreement. An overdue label does not impose a penalty, send a message or connect to a bank. It is a prompt for your own checking and communication.

3. Work through an example

If the customer reports sending the other 400 but you have not verified it, that amount remains in the confirmed outstanding balance. These dates are only for testing.

4. Set up your account and start the build

1. Use your account or register.Visit www.gammal.tech/join. New account activation takes 1–10 days. Use a National ID from a country whose citizenship you hold; the official account guide explains the limited exceptions for Egyptian citizens. Submit identity documents only through the official registration process.
2. Activate the WhatsApp subscription.After approval, open my.gammal.tech and add EGP 200 to your wallet, or use sufficient existing funds. Activate the monthly WhatsApp subscription in your account and check that it is active. Funding the wallet alone does not activate it. This subscription covers light personal use; website creation is charged separately.
3. Open the building conversation.Message +201033998844 and send the following command by itself, including the required square brackets. Wait for confirmation of build mode:

   [mode: build]

   [mode: web] is an alternative for the same mode; you only need one command.
4. Send the request in the next section.Replace its placeholders and ask for exactly one page using an available name of at least three characters. Before execution, request an itemised quote separating the one-time build fee, EGP 100 for the first month of standard hosting and any additional usage. Ask how changes beyond the agreed scope are charged.
5. Check the total and approve the build.Once you understand the quote, return to your account and add any missing funds. Return to WhatsApp and confirm the scope and price. Some simple sites take minutes; requirements and revisions affect timing. Open the resulting address and run this guide’s acceptance checks.
6. Record the renewal date.MeNooN hosting renews manually: select the duration and confirm payment before expiry. Leaving funds in your wallet does not renew it automatically. Send [exit], including brackets, when you finish the building conversation.

Budget: quoted build fee + EGP 100 hosting + EGP 200 for one WhatsApp month if it is not already active, plus agreed usage. Twelve months of standard hosting cost EGP 1,200; adding one WhatsApp month makes EGP 1,400 before build and usage fees. Keeping WhatsApp active for further months costs separately.

For private saving, ask the builder to connect Gammal Tech sign-in and register the correct website address in your project. If requested, open the developer area, select the project or create it under the agreed quote, and copy its ID; never guess it. Check that the final site address is registered before testing saves. Each account has its own data. Test save and reload, then ask a trusted person using their own genuine account to check that your records are not visible. Do not share sign-in codes or create another account for yourself. User-data storage is free, with a 1 MB limit per user, so keep short text records rather than files or photographs. Paid sign-in codes may need project funds after the free allowance: fund your wallet, then transfer a usage budget to the project in the developer area. Sign-in does not automatically disclose identity or contact details to the site owner.

Open the developer area

Service steps and prices reviewed on 18 October 2026. Check the amount shown in your account before paying. WhatsApp steps · Hosting and renewal

5. Adapt and send this request

Replace every bracketed placeholder with your real details. Copy this request after the assistant confirms build mode. Do not publish the illustrative figures as your own.

Build a private single-page payment due tracker called [tool name]. Use Gammal Tech login and separate per-user storage. Record a short project label, agreement total, currency and instalments with amounts and due dates. Keep customer payment reports separate from receipts I manually verify. Assign each verified receipt entry to a specific instalment, with an amount, date and short reference; allow partial receipts. Calculate the remaining balance only from verified amounts and distinguish due today, overdue and upcoming amounts against a visible review date. Do not connect to banks, InstaPay or Vodafone Cash, accept screenshots as verification or promise automatic reminders. Reject negative amounts and flag duplicate receipt references or totals above the agreement for review. Record correction reasons rather than hiding previous mistakes. Do not collect identity, card or login credentials. This is a single-owner register, not a shared client portal. Make it easy to use on a phone. Before execution, quote the one-time build cost separately from the first month of standard one-page hosting at EGP 100, explain additional usage charges and wait for approval.

6. Test the result before relying on it

1. Create three 1,000 instalments. Assign a verified receipt of 1,000 to the first, 600 to the second and none to the third.Expected result: The register shows 1,600 received and 1,400 remaining. The second instalment is only partly paid.
2. Use 11 November as the review date with due dates of 1, 10 and 20 November.Expected result: It shows 400 overdue and 1,000 upcoming. The completed first instalment contributes nothing to overdue balances.
3. Record a reported but unverified 400, then try a negative amount and a duplicate receipt reference.Expected result: The report does not reduce the balance; negative input is rejected and duplication requires review before counting again.
4. Save, sign out and sign back in, then inspect the page while signed out.Expected result: Your records return within your account. No amounts or receipt references are displayed publicly.

7. Use the project during its first week

Reserve ten minutes twice during the first week to compare the tracker with the receipt sources you verify yourself. Start with two agreements so partial and overdue states remain easy to inspect. Do not mark an instalment complete simply because its date passed or a message arrived. Note which agreements need a polite enquiry, then communicate through your normal channel. At the end of the week, reconcile verified receipts with your references and review corrections or duplicates. This is a personal organising register, not a bank statement or independent proof of payment.

Your first weekly review note

Payment review note: [website link]. The verified remaining balance is [amount], including [amount] past its agreed date. I will check [reference] before changing its status and manually follow up on agreements needing attention.

Questions about this project

Is a transfer screenshot enough to confirm receipt?

Not by itself in this workflow. Record the report, verify receipt through your normal account-checking process, then enter the amount and date. The tool does not authenticate images or transfers.

Will the tracker send reminders?

Not in this project. Review it at a fixed time and contact customers yourself. Future automation would require a separately verified channel, workflow and cost.

What should I do with an apparent overpayment?

Investigate before recording it as additional money for this agreement. It could be duplication or belong to another project. Keep any correction explicit rather than changing the contract total automatically.