WEBVTT

00:00:01.300 --> 00:00:05.179
A request describes what you asked for. A fill describes an amount

00:00:05.179 --> 00:00:09.059
that actually executed. Keeping those ideas separate is one of the most

00:00:09.059 --> 00:00:12.938
useful habits in the app. We have sent an example Paper buy.

00:00:12.938 --> 00:00:16.817
Now we will check the evidence instead of judging success by whether

00:00:16.817 --> 00:00:20.050
a dialog disappeared or a number briefly flashed on screen.

00:00:20.550 --> 00:00:24.329
Return to Portfolio in the same Paper context. Find the complete pair

00:00:24.329 --> 00:00:28.108
and inspect the position quantity. If you already held that asset, compare

00:00:28.108 --> 00:00:31.887
the new amount with the amount before the request. Do not expect

00:00:31.887 --> 00:00:35.666
every buy to create a separate visible row. An existing position may

00:00:35.666 --> 00:00:39.445
be updated, so the change in quantity matters more than the number

00:00:39.445 --> 00:00:40.075
of rows.

00:00:40.575 --> 00:00:44.402
Keep the position's identity in view. Where owner, strategy, or account information

00:00:44.402 --> 00:00:48.230
is available, use it to distinguish holdings that share a symbol. A

00:00:48.230 --> 00:00:52.057
manual purchase and a strategy-owned holding should not be treated as the

00:00:52.057 --> 00:00:55.885
same position just because both show the name Bitcoin. When you later

00:00:55.885 --> 00:00:59.712
sell, you will need the specific holding, not a guess based on

00:00:59.712 --> 00:01:00.350
its name.

00:01:00.850 --> 00:01:04.785
Next, open Transactions and look for the relevant recorded activity. Check the

00:01:04.785 --> 00:01:08.720
mode, filters, pair, buy direction, time, and quantity where shown. Compare any

00:01:08.720 --> 00:01:12.655
displayed execution price, value, and fees with the record itself. Do not

00:01:12.655 --> 00:01:16.590
fill in a missing field from memory or copy the earlier price

00:01:16.590 --> 00:01:20.525
estimate into your notes as though it were a confirmed execution price.

00:01:21.025 --> 00:01:24.737
Suppose our illustrative request was for zero point two units. If the

00:01:24.737 --> 00:01:28.449
recorded result confirms zero point two and the matching holding increases by

00:01:28.449 --> 00:01:32.161
that amount, the two views agree about the quantity. If only zero

00:01:32.161 --> 00:01:35.873
point one is confirmed, that is the amount you can account for

00:01:35.873 --> 00:01:39.585
so far. A partial outcome means some of the requested amount executed,

00:01:39.585 --> 00:01:41.750
not that the rest must eventually follow.

00:01:42.250 --> 00:01:46.332
You may encounter words such as accepted or pending in an order

00:01:46.332 --> 00:01:50.414
result. Accepted means the request was received for handling; it does not

00:01:50.414 --> 00:01:54.496
prove a fill. Pending means confirmation is still outstanding. A rejection means

00:01:54.496 --> 00:01:58.578
the request was not approved as submitted. Read the actual status available

00:01:58.578 --> 00:02:02.660
in that workflow rather than assuming every screen displays the same order-status

00:02:02.660 --> 00:02:03.000
table.

00:02:03.500 --> 00:02:07.463
A confirmed execution and a refreshed account display can also arrive at

00:02:07.463 --> 00:02:11.426
different times. If the app says internal accounting is still pending, wait

00:02:11.426 --> 00:02:15.389
for the records to settle before starting another sale. If an order

00:02:15.389 --> 00:02:19.352
ended, inspect the filled amount: ended does not necessarily mean filled in

00:02:19.352 --> 00:02:23.315
full. The purpose of checking both activity and holdings is to catch

00:02:23.315 --> 00:02:23.975
these differences.

00:02:24.475 --> 00:02:28.317
Finish your review with a short record of what you know: the

00:02:28.317 --> 00:02:32.159
request, the confirmed quantity, the matching position, and anything still unresolved. If

00:02:32.159 --> 00:02:36.001
the evidence does not agree, label the result uncertain and investigate. You

00:02:36.001 --> 00:02:39.843
do not need to force every attempt into success or failure immediately.

00:02:39.843 --> 00:02:43.685
A precise description of what is known is more useful than an

00:02:43.685 --> 00:02:44.325
early conclusion.