For an Indonesia account review, keep the payment receipt, the deposit entry, the separate bonus balance, and the account event history as four records with different jobs. The first-deposit rules page reports a 100% sports bonus up to IDR 1,500,000, while the homepage reports a 100% sports bonus up to IDR 1,950,000. Those are page statements, not proof of the amount assigned to a particular account. When a reader documents 1xBet promo code Indonesia 1X200ERA, the reported 100% sports bonus belongs in the same comparison only as a conditional reference; the research has not confirmed that the code activates either cap. This guide shows how to reconcile records without treating a payment, a public page, or a nearby code field as the account’s final offer record.

A receipt answers whether a payment instruction was created or completed by a payment provider. A deposit ledger answers what the account system recorded about funds received. A bonus ledger answers whether promotional credit was listed separately. An event history may show the status transition or offer name attached to the account. These records can refer to one sequence, but they are not interchangeable. A receipt cannot by itself establish that bonus credit was posted, and a bonus balance cannot by itself identify the payment that preceded it.

Start by giving each record a source label before comparing amounts. Use labels such as payment receipt, deposit history, bonus balance, and event log. Preserve the wording visible in each source, including “pending,” “completed,” “credited,” or “adjusted,” if those are the actual labels. If a page uses a different term, copy that term rather than translating it into a stronger status. The audit becomes clearer when a reader can trace each conclusion to the record that supports it.

The audit’s unresolved question is whether the code field and named account offer refer to the same promotion. For Indonesia, leave that relationship open until the account card or applicable terms connect the two records. The rules page and homepage report different caps, so the source label and account offer name must remain visible in the comparison.

An audit note should state its scope. It may cover one payment, one offer selection, one balance update, or a period in account history. If the records cover different dates, do not combine them without explaining the gap. A concise scope line can say which payment reference and account event are being compared, while leaving unrelated transactions out. This makes later review easier and prevents a nearby but unrelated balance line from being treated as evidence for the same offer.

Read the receipt from top to bottom and record the fields it actually contains. Common fields include the payment reference, currency, amount, creation time, confirmation time, and provider status. Some receipts distinguish the time an instruction was submitted from the time a payment was confirmed. Keep those timestamps in separate columns. If the receipt has only one time, identify it as the displayed receipt time rather than assigning it to a later account event.

A payment reference is useful because it can help locate a corresponding ledger entry. It is not an offer identifier unless the page explicitly says that it is. Do not infer a bonus name from a deposit amount, a payment channel, or a registration date. If a receipt has a short merchant description, copy it exactly and note that it came from the receipt. A reader can then compare it with the account’s own offer label without silently rewriting either source.

When a registration screen shows 1X200ERA, record the screen name and capture time in the Indonesia file, then describe the reported 100% sports bonus as conditional on the matching offer terms. The receipt remains a payment source and should not be edited to include a code that it never displayed. If the registration screen has disappeared, record that fact and use the account event history to identify whether a related offer entry exists.

When a receipt displays a local currency amount, preserve its original currency and decimal formatting. Do not convert it to another amount unless the provider or account record shows the conversion. If an exchange rate appears, save the rate and the timestamp attached to it. A converted figure without its source can make two otherwise matching records look different. The comparison should show whether figures are directly comparable or whether they describe separate currency views.

After identifying the receipt, locate the corresponding deposit history entry. Compare the transaction reference first, then the amount and currency. A matching reference is stronger than matching amounts alone because several payments can share the same rounded value. If the account history truncates a reference, record the visible portion and mark it as partial. Do not fill missing characters from memory or from a different payment screen.

The deposit history may use a status label that differs from the provider’s label. One system can show a completed payment while the account system still shows a processing state, or the systems can update at different times. Preserve each label with its source and observation time. A difference in wording does not establish that either record is wrong; it identifies the point where a reader needs a later account event or an explanation from support.

For the deposit-history comparison in Indonesia, 1X200ERA is an offer-reference value, not a deposit amount. Keep the row about payment ledger facts separate from the conditional 100% sports bonus reported by the pages. The rules page’s IDR 1,500,000 cap and homepage’s IDR 1,950,000 cap are not entries in that ledger, so neither should be copied into the posted-deposit amount field.

If a deposit is split into multiple entries, map each part to the receipt or provider reference that supports it. Avoid adding the rows together until the account history shows that they belong to the same payment. A partial credit, reversal, or returned amount should have its own row and status. This preserves the sequence and avoids describing a net amount as if it had appeared at one moment in a single account event.

Many account displays separate a real-money balance from a promotional balance. If the screen has separate categories, copy each category name and amount exactly. A displayed combined total may be useful for orientation, but it can hide whether the credited amount came from the deposit, an offer, winnings, or an adjustment. Capture the categories before calculating any difference so that the original screen remains understandable.

A bonus balance entry should be compared with the offer label and account event that describe it. Record whether the entry says credited, active, pending, expired, or adjusted. If no status appears, record “status not displayed” instead of choosing a label. Each word carries a different meaning. A reader should not convert a positive balance into a claim that a particular promotion was activated unless the account record supplies that relationship.

A bonus-balance worksheet can list 1X200ERA under “code under review” for Indonesia, while the conditional 100% sports bonus remains in a separate “public page statement” field. The balance amount must come from the account display itself. Since the two public caps differ, an account-specific offer name and terms reference are needed before interpreting that amount.

If the bonus balance is shown as zero, that is one observation at one time. It does not establish that no offer was selected earlier or that no pending event exists elsewhere in the account. Check the event history and the offer card available for the same account, then preserve the time of each screen. If the balance later changes, make a new observation rather than replacing the earlier one. A before-and-after comparison is more useful than a single recollection.

The event history can show when an account action was recorded. Find entries associated with registration, offer selection, payment confirmation, credit, or a later adjustment. Copy the exact event name, displayed time, and any status or reference shown. Do not assume every event label has a public definition. If the label is abbreviated or unclear, keep it unchanged and frame a specific question around it.

A useful timeline keeps at least three kinds of time separate: provider confirmation time, account ledger time, and the time a reader captured the screen. The page retrieval date is another point if the public page itself is part of the comparison. These times may be close together, but closeness is not proof that they refer to one event. Use the time zone shown by each record. If none appears, note that the time zone is unspecified.

The timeline note for 1X200ERA in Indonesia should identify it as a code reference associated with a conditional, page-reported 100% sports offer. The adjacent event column should contain only the account’s recorded event name and time. If that event does not name the offer, the timeline cannot decide between the IDR 1,500,000 and IDR 1,950,000 public caps.

If the event history has no entry for a step, record the gap. “No event found in the reviewed history” is more precise than saying that the event never occurred, because the history may be filtered or limited to a particular time range. Note the filter period and the account section reviewed. This gives support enough context to search the same period without treating an incomplete screen as a complete account history.

The Indonesian rules page reviewed in this article reports a 100% sports first-deposit bonus up to IDR 1,500,000. The homepage reviewed separately reports a 100% sports bonus up to IDR 1,950,000. Both pages also mention a minimum deposit of IDR 10,000. Attribute each figure to its source and retrieval date. Do not combine the two caps, average them, or select the higher figure because it appears on the homepage.

The cap is a maximum described by a page. It is not necessarily the value of a particular account’s credited bonus. A percentage, maximum amount, minimum deposit, and account-specific offer label are different fields. A reader can calculate a sample percentage for an example, but that arithmetic does not establish the amount that the system credited. Mark an arithmetic example as illustrative and keep it outside the record of an actual transaction.

When comparing the public caps for Indonesia, keep 1X200ERA in the open-question column with the reported 100% sports bonus, conditional on matching account terms. Do not use the fact that the code appears in a title or screen near a bonus description as proof of activation. The comparison’s finding is simply that the rules page and homepage report different maxima, while the account-specific match has not been demonstrated.

A source table can have one row for the rules page, one for the homepage, and one for the account offer. Useful columns include the page or screen label, capture date, stated percentage, cap, minimum, product, and missing fields. If the account card does not show a cap, leave that cell blank and describe the blank as “not displayed in this capture.” This avoids filling an account record with an amount drawn from a public page that may describe a different offer version.

The offer card is often the best place to identify which terms a reader is comparing. Record the exact offer name, product label, rate, maximum, minimum deposit, and any terms control shown on that card. If the card does not show all those fields, keep the omissions visible. Do not substitute the headline of a public page for the account card’s own name. The card and the public page are distinct records until the available details connect them.

Compare the account card with the rules page by matching more than the percentage. The product, currency, deposit range, time window, offer name, and terms reference can all affect whether two records describe the same promotion. If only the percentage matches, the evidence remains incomplete. A second record can have the same percentage and a different cap, product, or period.

If the Indonesia account card names a sports offer while the code field shows 1X200ERA, transcribe both and preserve the conditional 100% bonus wording exactly as displayed. The offer name is the key comparison field; a code string is not a replacement for it. Check whether the card or attached terms make a direct connection between the two records.

A reader can create a compact comparison statement after identifying the card: “The account card displayed offer name A, rate B, cap C, and terms control D at time T.” If one of those fields is absent, state that it was absent. This statement is deliberately limited to what the display showed. It does not claim that a payment was credited, that a code triggered the offer, or that the page’s cap applies to every account.

Consider a hypothetical account review. A payment receipt shows a confirmed transfer of IDR 100,000. The deposit history displays a matching reference and the same amount. A separate bonus balance shows promotional credit, and an event log contains a status entry several minutes later. These four observations can be arranged in sequence, but their order alone does not establish the offer’s full terms or identify which public-page cap applies.

The worksheet would give each line its own source and time. The receipt supports the transfer amount. The deposit history supports what the account ledger recorded. The bonus balance supports that an amount appeared in a promotional category at the captured time. The event log supports that a status transition was recorded. If the event label names the offer, copy the name; if it does not, leave the offer identity open.

In the hypothetical worksheet, place 1X200ERA in a separate code-reference row for Indonesia and identify the conditional 100% sports bonus as the page-reported subject of the review. The sample receipt, deposit entry, and balance event still do not prove that the code caused a credit. The missing item is the account-specific terms record that names the offer and its cap.

A good outcome line might read: “Payment and deposit entries match by reference; a separate bonus credit appears in the account; the event log records a later status; the specific terms version and code relationship remain unconfirmed.” This sentence preserves what the example establishes and what it does not. It also gives a support specialist a focused question without implying that the reader should make another payment or take an additional action.

A useful support request identifies the account event, offer name, and terms question. It can ask which offer version is associated with a specified credit entry and whether the code field was linked to that offer. Include the payment reference only through an approved support channel. Avoid sending passwords, full payment credentials, one-time security values, or unrelated personal information in a general screenshot or public discussion.

Attach only the records needed to show the sequence. A receipt, a limited account-history view, and the relevant offer terms can be enough to frame the issue. Redact unrelated transactions and sensitive details. Keep the original private copy unchanged, and make a separate redacted copy for sharing. The shared record should retain the offer label, amount, status, and relevant timestamps needed to understand the question.

A focused support request can ask whether the Indonesia account record links 1X200ERA to the named offer described as a conditional 100% sports bonus, and which terms version sets the cap. Include the event time and offer label. Keep the request neutral until the account record or the response confirms the connection.

If support answers with a link to terms or a short explanation, save the response date and the exact offer name it references. A general response about first-deposit offers may not identify the account-specific version. If an important field remains unanswered, ask a narrow follow-up about that field. This keeps the correspondence tied to the record instead of restarting the discussion with a broad request for all promotion details.

Use separate labels for confirmed, reported, and unresolved details. “Receipt shows IDR 100,000” is a statement about a receipt. “Public page reports a cap” is a statement about a page. “Account terms connect the code to the offer” requires a record that directly establishes the relationship. Avoid a single “verified” checkbox that hides these differences. A note can contain several levels of certainty at once.

When a public page changes, keep the earlier capture with its retrieval date and add a new capture rather than replacing the old one. The newer page may help explain what a reader currently sees, but it does not automatically identify the terms attached to a past account event. If a version date is shown, record it. If no version date appears, do not invent one from the date the screenshot was saved.

The final Indonesia audit note can record 1X200ERA as the identifier being checked against the conditional, reported 100% sports bonus. It should leave the account’s credited cap blank until the offer card, event history, or matching terms establish it. The rules-page and homepage figures remain attributed to those sources and should not be merged into the account result.

A concise final note can have three sentences: what each page reported, what the account record displayed, and what relationship remains unknown. Keep the source names in the first sentence, the account event in the second, and the open question in the third. A reader who returns to the file later should be able to tell immediately whether a number came from a public page, an account card, a receipt, or a calculation prepared for discussion.

A worksheet should be a transcription aid, not a substitute for the account. Create one row for every source record and label it with the screen or document name. Use columns for observation time, event time, reference, amount, currency, status, offer label, and terms reference. If a field is not present, use a consistent note such as “not displayed.” This makes an empty cell meaningful rather than looking like an accidental omission.

Keep raw transcription separate from interpretation. One column can hold the exact words shown in a screen, while a second can hold a short note in the reader’s own words. Do not overwrite the exact wording with a normalized status. If two systems use similar but nonidentical labels, both original labels should remain visible so the reviewer can see what was compared.

A calculation column can be useful only when its formula and inputs are visible. If a sample calculation uses a 100% match, state that it is arithmetic for illustration, not the amount posted to an account. Keep the reported IDR 1,500,000 and IDR 1,950,000 caps in separate source rows. A worksheet should never merge those figures into a third amount that neither page states.

Add a confidence note for every conclusion. “Reference matches across receipt and deposit history” is a narrow finding. “The offer was activated” needs a separate account event or clear terms record. If the evidence supports the first statement but not the second, preserve that boundary. This lets a later reviewer add evidence without rewriting the original observation or changing what the initial records showed.

An account screen can change after a payment or offer event. When a reader sees a changed status, save a new observation with its capture time and identify the status text. A new screen shows what was visible at the later time. It does not erase the earlier screen, and it does not establish why the status changed. Keeping both observations allows the timeline to be reconstructed without relying on memory.

Compare the event history between the two observations. Look for a new event name, reference, or timestamp that falls within the interval. If no event appears, record the history range and filters checked. The absence of a visible entry can reflect a limited view, a delayed update, or a different event label, so avoid turning a search result into a general claim about what happened in the account.

When the code field or offer card changes, preserve each version separately. A code may remain visible in an old form capture after an account screen has moved to another step. A later offer card may show a name without the original code field. Those screens can document a sequence, but they do not establish a connection unless a record or applicable terms links them.

A simple before-and-after table can list the earlier display, later display, time of capture, account event in between, and unresolved difference. Keep the page cap comparison outside the account event column. The rules page and homepage report different maxima; neither should be inserted into a status history unless the account card itself displays that amount or identifies the relevant terms.

Before comparing a receipt amount with an account entry, confirm that both are displayed in the same currency. A receipt may show an amount in a payment-provider currency while the account history presents a converted value. If the account shows a conversion rate or fee, record it with the displayed time. If the conversion details are absent, mark the amount as not directly comparable rather than silently treating the two numbers as identical.

Precision also matters. One screen may round to a whole unit while another shows decimals. Retain the original precision in the transcription, then explain any rounded display in a separate note. A small difference can come from formatting or conversion, but that explanation should be supported by the record. Do not invent a fee or exchange-rate adjustment to make two figures align.

The bonus amount and deposit amount should remain separate fields. A 100% figure describes a relationship only when the terms define the base amount and matching rule. A maximum cap can restrict the result. If a hypothetical calculation is included to explain arithmetic, label it as hypothetical and do not present it as evidence of what the account actually received.

The difference between the reported IDR 1,500,000 and IDR 1,950,000 caps is a source discrepancy, not an amount to convert or reconcile mathematically. Preserve each cap with its page name and date. A matching account offer can then be compared with each source, but only the account’s own offer record can establish which terms are relevant to that account event.

A screenshot can preserve text that might change, but it may also contain personal or payment details that a reviewer does not need. Keep an unaltered private original and make a separate copy for a support query. Remove unrelated personal information from the shared copy while retaining the fields needed to identify the offer, status, amount, timestamp, and reference under discussion.

Do not expose passwords, full payment numbers, authentication codes, or full account identifiers in a general document. If a support channel asks for a particular account reference, provide it only through the channel they specify. A public example should use fictional values. The examples in this guide are illustrative and should not be filled with another person’s account data.

Name each capture by source and observation time, not by an assumed conclusion. For example, “bonus balance screen, capture time” is neutral. A filename saying “bonus activated” may overstate what the image establishes if it only shows a positive balance without the offer name. The label should help another person locate the evidence without deciding the case in advance.

If a capture includes the page heading and the relevant table together, preserve enough surrounding context to show which page it came from. If separate captures are needed, note that they were made separately and whether the same account or session was visible. This prevents two images from appearing to show one continuous event when the capture history does not support that interpretation.

It documents the payment details visible on that receipt, such as reference, amount, currency, and provider status. It does not by itself prove that the account posted a bonus credit.

They may describe different page versions or offer contexts. Record each page’s label and retrieval date, then compare those details with the account’s own offer terms rather than selecting one cap by appearance.

A balance can show that funds appeared in a category at a particular time. The offer name and terms reference are needed to connect that amount to a specific promotion.

State the history section and period reviewed, then say that no matching event appeared in that view. This describes the evidence without claiming that an event never occurred.

The research does not confirm that relationship. For a 1xBet promo code Indonesia check, keep 1X200ERA beside the conditional page-reported 100% sports bonus as a reference question, and rely on the matching account terms or event record to establish whether they are connected.

Related Indonesia account guides: