WEBVTT

00:00:01.300 --> 00:00:05.353
Reconcile means compare records until you can explain how they fit together.

00:00:05.353 --> 00:00:09.405
After an exit, you want to connect the requested action, the recorded

00:00:09.405 --> 00:00:13.458
fill, and the remaining holding. The goal is not to force every

00:00:13.458 --> 00:00:17.511
number to look identical. It is to understand why each number has

00:00:17.511 --> 00:00:20.550
its value and leave any unresolved difference clearly identified.

00:00:21.050 --> 00:00:25.105
Open Recent Fills to inspect recent recorded activity. Read the time, symbol,

00:00:25.105 --> 00:00:29.159
source or strategy badge, buy or sell direction, reason, and amount where

00:00:29.159 --> 00:00:33.214
shown. A sale may also include a separate realized P and L

00:00:33.214 --> 00:00:37.269
figure. That smaller result is different from the sale amount itself. Remember

00:00:37.269 --> 00:00:41.323
our example: eighty-eight dollars of gross proceeds can include only eight dollars

00:00:41.323 --> 00:00:42.675
of gain before fees.

00:00:43.175 --> 00:00:47.042
Recent Fills is a short recent feed, not your entire account history.

00:00:47.042 --> 00:00:50.908
A missing event may be outside the visible recent set. The feed

00:00:50.908 --> 00:00:54.775
can also show a delay notice depending on access. Read that notice

00:00:54.775 --> 00:00:58.642
before comparing it with a newer portfolio update. An event missing from

00:00:58.642 --> 00:01:02.508
a delayed or limited feed is not enough evidence to conclude that

00:01:02.508 --> 00:01:03.475
it never happened.

00:01:03.975 --> 00:01:08.464
Use Transactions for a broader check of the recorded activity. Match the

00:01:08.464 --> 00:01:12.954
selected mode and account, then review the relevant date range, filters, asset,

00:01:12.954 --> 00:01:17.443
side, quantities, prices, and fees where available. Compare identifying references when supplied.

00:01:17.443 --> 00:01:21.932
Two nearby sales of the same asset are not automatically the same

00:01:21.932 --> 00:01:24.925
event, especially when separate strategies hold that asset.

00:01:25.425 --> 00:01:28.960
For our fictional partial sale, begin with ten units and a confirmed

00:01:28.960 --> 00:01:32.495
executed quantity of four units. With no other activity, you would expect

00:01:32.495 --> 00:01:36.029
six units remaining. If you instead see ten units, check the portfolio's

00:01:36.029 --> 00:01:39.564
freshness and the action status. If you see a different quantity, inspect

00:01:39.564 --> 00:01:43.099
for other fills or adjustments. Explain the difference from records rather than

00:01:43.099 --> 00:01:45.750
assuming the first number you saw must be wrong.

00:01:46.250 --> 00:01:50.633
The desktop portfolio includes snapshot information and Sync Now. A refresh or

00:01:50.633 --> 00:01:55.016
sync helps request updated information; it does not create a missing fill,

00:01:55.016 --> 00:01:59.399
reverse an order, or guarantee that every service updates at the same

00:01:59.399 --> 00:02:03.782
instant. Read any error or unknown timestamp honestly. Also check hidden-small-holding settings

00:02:03.782 --> 00:02:07.800
and search filters before concluding that the remaining position has vanished.

00:02:08.300 --> 00:02:12.158
For a Live order that remains unclear, inspect the same connected exchange

00:02:12.158 --> 00:02:16.017
account's order and fill history. Compare the order reference, time, executed quantity,

00:02:16.017 --> 00:02:19.875
and status with the app. Keep an uncertain request separate from a

00:02:19.875 --> 00:02:23.734
new trading decision. Repeatedly submitting a fresh sale is not a reconciliation

00:02:23.734 --> 00:02:27.592
method, because the earlier request may already have executed even if the

00:02:27.592 --> 00:02:29.200
display has not caught up.

00:02:29.700 --> 00:02:33.914
If the records still do not explain the difference, gather useful evidence

00:02:33.914 --> 00:02:38.129
for support: mode, account label without sensitive details, asset, time, request reference,

00:02:38.129 --> 00:02:42.343
visible status, and sanitized screenshots. Never include API secrets or recovery codes.

00:02:42.343 --> 00:02:46.557
Your conclusion can be that the outcome remains unverified. A precise unanswered

00:02:46.557 --> 00:02:50.771
question is more useful than a confident guess about missing funds or

00:02:50.771 --> 00:02:51.825
a completed exit.