WEBVTT
1
00:00:00.540 --> 00:00:02.130
So good morning everyone.
2
00:00:02.130 --> 00:00:04.200
This is Alex Absara with Fiscal Service.
3
00:00:04.200 --> 00:00:07.560
And today, I know it's kind of been an ongoing topic for us,
4
00:00:07.560 --> 00:00:09.780
but it's about reporting functionality
5
00:00:09.780 --> 00:00:12.510
that we have in GTAS and G-Invoicing.
6
00:00:12.510 --> 00:00:14.520
And this might be something that you've heard about.
7
00:00:14.520 --> 00:00:18.180
We tried to present this during last calendar year,
8
00:00:18.180 --> 00:00:20.390
I think in the fall during third quarter scorecard meeting
9
00:00:20.390 --> 00:00:22.064
to really get the topic out there,
10
00:00:22.064 --> 00:00:24.450
make sure everyone's aware about the functionality,
11
00:00:24.450 --> 00:00:27.553
but really what's coming up here in quarter two
12
00:00:27.553 --> 00:00:30.660
for fiscal year '23 and the scorecards
13
00:00:30.660 --> 00:00:32.760
is there's gonna be a new metric presented
14
00:00:32.760 --> 00:00:33.593
around G-Invoicing
15
00:00:33.593 --> 00:00:36.284
and how basically monitoring agency progress
16
00:00:36.284 --> 00:00:41.284
with the mandate that was effective as of 10/1/2022
17
00:00:41.940 --> 00:00:43.535
for new orders.
18
00:00:43.535 --> 00:00:47.007
So with that, with that being on the scorecard,
19
00:00:47.007 --> 00:00:50.160
we had to figure out a way, here at Fiscal Service,
20
00:00:50.160 --> 00:00:51.780
to really monitor compliance
21
00:00:51.780 --> 00:00:53.790
the progress agencies were making
22
00:00:53.790 --> 00:00:55.340
with their G-invoicing reporting.
23
00:00:55.340 --> 00:00:58.728
I'm getting a little feedback there.
24
00:00:58.728 --> 00:01:01.278
But really had to figure out a way to monitor that.
25
00:01:03.023 --> 00:01:05.190
Give me a moment, Alex.
26
00:01:05.190 --> 00:01:07.637
I'm gonna just, as a warning for everyone,
27
00:01:07.637 --> 00:01:09.870
I'm gonna mute all.
28
00:01:09.870 --> 00:01:13.860
So if you're dialed in by phone,
29
00:01:13.860 --> 00:01:15.600
you're gonna have to hit star six to come off mute.
30
00:01:15.600 --> 00:01:16.833
That includes you, Alex.
31
00:01:20.220 --> 00:01:22.560
Okay, muted all the lines now.
32
00:01:22.560 --> 00:01:27.000
And then if anyone does wanna come off mute to engage,
33
00:01:27.000 --> 00:01:28.110
feel free to do so.
34
00:01:28.110 --> 00:01:29.580
You also have the option
35
00:01:29.580 --> 00:01:32.490
to enter your questions in the chat.
36
00:01:32.490 --> 00:01:34.113
So sorry Alex, back to you.
37
00:01:34.980 --> 00:01:36.030
All right, thanks Robert.
38
00:01:36.030 --> 00:01:37.110
Thanks for doing that.
39
00:01:37.110 --> 00:01:39.570
Definitely makes it easier without the feedback.
40
00:01:39.570 --> 00:01:41.760
So when I was talking previously,
41
00:01:41.760 --> 00:01:43.110
we were basically saying we had to figure out
42
00:01:43.110 --> 00:01:44.820
a way to monitor the progress
43
00:01:44.820 --> 00:01:46.710
and compliance with the mandate.
44
00:01:46.710 --> 00:01:49.280
And what we really set up was we figured out
45
00:01:49.280 --> 00:01:53.820
or created a way to interface G-invoicing information
46
00:01:53.820 --> 00:01:56.490
into GTAS for nine data points.
47
00:01:56.490 --> 00:02:00.960
And within GTAS, we created nine proposed analytical edits
48
00:02:00.960 --> 00:02:02.939
to compare what was being reported
49
00:02:02.939 --> 00:02:05.370
with transactional activity in G-invoicing
50
00:02:05.370 --> 00:02:07.980
compared to what was being reported
51
00:02:07.980 --> 00:02:11.520
on your just trial balance block file in GTAS.
52
00:02:11.520 --> 00:02:13.380
So when we're comparing that information,
53
00:02:13.380 --> 00:02:16.290
we can really see the overall reporting
54
00:02:16.290 --> 00:02:17.130
that was happening in GTAS
55
00:02:17.130 --> 00:02:19.140
compared to what was happening in G-Invoicing
56
00:02:19.140 --> 00:02:21.180
and really put a percentage behind that
57
00:02:21.180 --> 00:02:22.500
to see the overall compliance
58
00:02:22.500 --> 00:02:25.020
and progress agencies were making.
59
00:02:25.020 --> 00:02:27.330
So one thing we heard when we started talking
60
00:02:27.330 --> 00:02:29.250
about putting out this metric on the scorecard
61
00:02:29.250 --> 00:02:32.769
was agencies wanted a way to really dive in the details
62
00:02:32.769 --> 00:02:35.872
and reconcile the data between the two systems.
63
00:02:35.872 --> 00:02:38.520
So what we did, and you're gonna hear more about
64
00:02:38.520 --> 00:02:41.359
from Jeff Board and Justin Sheline is how, I guess,
65
00:02:41.359 --> 00:02:43.380
there's different reporting functionality
66
00:02:43.380 --> 00:02:44.914
in both systems that you can use in unison
67
00:02:44.914 --> 00:02:48.090
to really reconcile any differences that you have
68
00:02:48.090 --> 00:02:49.440
and discrepancies you have
69
00:02:49.440 --> 00:02:51.690
between the two systems to do that.
70
00:02:51.690 --> 00:02:53.340
So really we're gonna dive into the details
71
00:02:53.340 --> 00:02:56.550
of what reporting capability we have in G-Invoicing
72
00:02:56.550 --> 00:02:58.578
and then what we're gonna have in GTAS
73
00:02:58.578 --> 00:03:01.200
to basically wrap all that data up
74
00:03:01.200 --> 00:03:03.240
and reconcile and really improve your metric
75
00:03:03.240 --> 00:03:05.130
that you have on the scorecard.
76
00:03:05.130 --> 00:03:05.963
But like I mentioned,
77
00:03:05.963 --> 00:03:07.470
this is gonna be a new metric as of Q2.
78
00:03:07.470 --> 00:03:10.290
So coming up for this period,
79
00:03:10.290 --> 00:03:11.943
period six reporting in GTAS.
80
00:03:12.870 --> 00:03:16.050
And when we do scorecards coming up in May,
81
00:03:16.050 --> 00:03:18.597
this will be on the scorecard and as Jeff
82
00:03:18.597 --> 00:03:20.670
and Justin walked through this,
83
00:03:20.670 --> 00:03:24.471
it'll really help you out on how you can improve
84
00:03:24.471 --> 00:03:27.609
the overall percentage rating we have
85
00:03:27.609 --> 00:03:29.550
on the scorecard as well.
86
00:03:29.550 --> 00:03:32.670
So I'm going to take a brief pause,
87
00:03:32.670 --> 00:03:33.900
see if there's any questions about that
88
00:03:33.900 --> 00:03:35.610
before I kick it over to Jeff Board
89
00:03:35.610 --> 00:03:38.223
to talk about the G-Invoicing functionality.
90
00:03:45.270 --> 00:03:48.633
Hi there, my name's Angela Wilson, I'm with NRC.
91
00:03:49.650 --> 00:03:52.890
Thank you so much for doing this for us.
92
00:03:52.890 --> 00:03:57.890
You spoke very quickly and I am trying to take some notes.
93
00:03:57.990 --> 00:04:01.980
I know this is gonna be recorded for us to go back,
94
00:04:01.980 --> 00:04:04.950
but if you could go just a tad bit slower,
95
00:04:04.950 --> 00:04:06.273
that would be great.
96
00:04:07.960 --> 00:04:09.990
Okay, is there any certain points you missed,
97
00:04:09.990 --> 00:04:11.439
Angela, that I could repeat or?
98
00:04:11.439 --> 00:04:14.049
No, no, I'm good for now.
99
00:04:14.049 --> 00:04:19.049
Just the pace was a little quick, thank you.
100
00:04:19.151 --> 00:04:21.990
I apologize about that.
101
00:04:21.990 --> 00:04:24.120
But yeah, if there's any other questions,
102
00:04:24.120 --> 00:04:25.800
feel free to speak up or if not,
103
00:04:25.800 --> 00:04:27.578
I'll kick it over to Jeff to jump
104
00:04:27.578 --> 00:04:29.562
into the G-Invoicing piece.
105
00:04:29.562 --> 00:04:32.477
Hey, good morning, this is Jose with BOP.
106
00:04:32.477 --> 00:04:36.510
I have one quick question regarding this reconciliation
107
00:04:36.510 --> 00:04:39.223
between G-Invoicing to GTAS.
108
00:04:39.223 --> 00:04:41.183
So I'm guessing that the G-Invoicing system
109
00:04:41.183 --> 00:04:44.730
is gonna talk back to Treasury within GTAS
110
00:04:44.730 --> 00:04:46.830
and it's gonna check for some edits.
111
00:04:46.830 --> 00:04:49.184
Are we expecting those edits to be analytical
112
00:04:49.184 --> 00:04:50.973
or fatal by Q2?
113
00:04:52.290 --> 00:04:53.220
So they're definitely
114
00:04:53.220 --> 00:04:54.330
gonna be proposing analytical,
115
00:04:54.330 --> 00:04:55.992
and that's definitely a good question,
116
00:04:55.992 --> 00:04:58.650
it's something that we've been asked in the past,
117
00:04:58.650 --> 00:05:00.150
but they're gonna be proposing analytical
118
00:05:00.150 --> 00:05:03.420
for the foreseeable future.
119
00:05:03.420 --> 00:05:05.580
We're not planning to take those fatal anytime soon
120
00:05:05.580 --> 00:05:08.310
probably until we have most activity in G-Invoicing
121
00:05:08.310 --> 00:05:11.250
and we're getting to a place where we feel comfortable
122
00:05:11.250 --> 00:05:12.360
with with making it fatal.
123
00:05:12.360 --> 00:05:14.340
But we'll definitely communicate that out
124
00:05:14.340 --> 00:05:15.900
to all federal agencies
125
00:05:15.900 --> 00:05:17.940
before we get close to taking that fatal.
126
00:05:17.940 --> 00:05:20.490
But really it's a proposed analytical edit.
127
00:05:20.490 --> 00:05:22.020
We're gonna be using it as like, as I mentioned,
128
00:05:22.020 --> 00:05:23.934
as a metric on the scorecard,
129
00:05:23.934 --> 00:05:26.100
but it'll definitely be proposed analytical
130
00:05:26.100 --> 00:05:29.310
and not cause you not to be able to certify
131
00:05:29.310 --> 00:05:31.160
your treasury account symbol in GTAS.
132
00:05:32.503 --> 00:05:34.156
Okay, thank you.
133
00:05:34.156 --> 00:05:36.156
You're welcome.
134
00:05:44.547 --> 00:05:47.763
All right, any other questions before Jeff takes over?
135
00:05:59.280 --> 00:06:00.810
Hi Jeff.
136
00:06:00.810 --> 00:06:03.180
All right, thank you Alex.
137
00:06:03.180 --> 00:06:04.013
Good morning everyone.
138
00:06:04.013 --> 00:06:05.910
This is Jeff Board from Fiscal Service.
139
00:06:05.910 --> 00:06:08.700
So I'm gonna do a quick little demo this morning,
140
00:06:08.700 --> 00:06:11.970
give you guys sort of a visual of the report
141
00:06:11.970 --> 00:06:14.100
that we have in G-Invoicing,
142
00:06:14.100 --> 00:06:16.920
kind of give you a look of how you can navigate to find that
143
00:06:16.920 --> 00:06:20.010
and then we'll walk through the data that's contained
144
00:06:20.010 --> 00:06:22.710
in that report and how that you'll be able to use that
145
00:06:22.710 --> 00:06:26.040
to try to reconcile your differences.
146
00:06:26.040 --> 00:06:27.181
So to start off the report
147
00:06:27.181 --> 00:06:29.160
that we've developed in G-Invoicing,
148
00:06:29.160 --> 00:06:31.410
it's called the ATB summary report,
149
00:06:31.410 --> 00:06:33.154
and it's gonna allow you to run reports
150
00:06:33.154 --> 00:06:36.630
by the accounting period in the TAS
151
00:06:36.630 --> 00:06:38.580
to identify which orders are associated
152
00:06:38.580 --> 00:06:41.073
with your IGT by cell differences.
153
00:06:42.028 --> 00:06:44.670
So this report's gonna provide agencies with information
154
00:06:44.670 --> 00:06:47.614
that is needed to go into the application,
155
00:06:47.614 --> 00:06:52.614
query up the orders or the 7600EZ invoices in G-Invoicing,
156
00:06:52.975 --> 00:06:55.380
just to kind of fully understand
157
00:06:55.380 --> 00:06:56.730
which performance transactions
158
00:06:56.730 --> 00:06:59.343
are involved in those differences.
159
00:07:00.339 --> 00:07:04.240
So this report became available with our 4.6 release
160
00:07:05.220 --> 00:07:06.840
and I did wanna mention that
161
00:07:06.840 --> 00:07:11.640
in order to access this report,
162
00:07:11.640 --> 00:07:13.200
the agency user must be assigned
163
00:07:13.200 --> 00:07:15.360
the TAS reconciler role in G-Invoicing.
164
00:07:15.360 --> 00:07:18.060
So if you don't have that TAS reconciler role,
165
00:07:18.060 --> 00:07:19.372
you'll wanna work within your agency
166
00:07:19.372 --> 00:07:21.235
to make sure you get that access
167
00:07:21.235 --> 00:07:23.580
to be able to query this report.
168
00:07:23.580 --> 00:07:25.947
So moving over to G-Invoicing,
169
00:07:25.947 --> 00:07:30.180
I'll just quickly show how we navigate to find this report.
170
00:07:30.180 --> 00:07:32.419
So in the dropdown, once you log in to G-Invoicing,
171
00:07:32.419 --> 00:07:35.043
you wanna make sure you're in the correct account,
172
00:07:36.090 --> 00:07:38.400
and then under the reports dropdown,
173
00:07:38.400 --> 00:07:42.450
you'll click there, and it'll list out the various reports
174
00:07:42.450 --> 00:07:43.948
that you have access to run.
175
00:07:43.948 --> 00:07:45.300
And like I said,
176
00:07:45.300 --> 00:07:47.670
if you don't have that TAS reconciler role,
177
00:07:47.670 --> 00:07:49.530
this ATV summary report's not gonna show up
178
00:07:49.530 --> 00:07:50.363
in your dropdown.
179
00:07:50.363 --> 00:07:53.580
So that's gonna be, you're kind of sign to know
180
00:07:53.580 --> 00:07:56.100
that you need to reach out to get that access
181
00:07:56.100 --> 00:07:58.980
if you don't see it present in that dropdown.
182
00:07:58.980 --> 00:08:00.960
Once you click ATB summary report,
183
00:08:00.960 --> 00:08:02.670
you're only gonna have two data fields to fill out.
184
00:08:02.670 --> 00:08:04.570
So you'll click the accounting period.
185
00:08:05.768 --> 00:08:09.240
Just for demonstration purposes, we'll pick March,
186
00:08:09.240 --> 00:08:10.740
and then over here you'll plug in
187
00:08:10.740 --> 00:08:13.410
your treasury account symbol.
188
00:08:13.410 --> 00:08:14.243
So like I said earlier,
189
00:08:14.243 --> 00:08:15.321
you can only run this report
190
00:08:15.321 --> 00:08:18.423
by one accounting period and one TAS.
191
00:08:19.500 --> 00:08:21.211
And it does have the type ahead feature.
192
00:08:21.211 --> 00:08:24.900
So if you want to start typing in
193
00:08:24.900 --> 00:08:27.870
like 020 for treasury and the ID,
194
00:08:27.870 --> 00:08:31.773
you can more easily locate the TAS involved.
195
00:08:32.670 --> 00:08:33.810
And once you select one,
196
00:08:33.810 --> 00:08:35.460
you'll just click this run report
197
00:08:36.690 --> 00:08:39.810
and it'll result something that looks similar to this.
198
00:08:39.810 --> 00:08:40.650
So I wanna just pause,
199
00:08:40.650 --> 00:08:42.720
make sure this is showing up big enough
200
00:08:42.720 --> 00:08:43.893
for everybody to see.
201
00:08:44.760 --> 00:08:46.743
If not, just let me know.
202
00:08:49.912 --> 00:08:51.270
All right, so I just wanted to quickly walk down
203
00:08:51.270 --> 00:08:53.160
through the report and show you the information
204
00:08:53.160 --> 00:08:55.110
that's gonna be contained here.
205
00:08:55.110 --> 00:08:58.200
So as I mentioned earlier, the parameters here,
206
00:08:58.200 --> 00:08:59.850
it'll call out the accounting period
207
00:08:59.850 --> 00:09:02.043
and the TAS that you've run the report for.
208
00:09:03.030 --> 00:09:07.530
And if you need to research more than one TAS
209
00:09:07.530 --> 00:09:09.341
or a TAS that is involved
210
00:09:09.341 --> 00:09:10.895
in more than one accounting period,
211
00:09:10.895 --> 00:09:13.263
you'll have to run multiple reports.
212
00:09:14.460 --> 00:09:17.833
As far as the data, I'll just kind of walk across the screen
213
00:09:17.833 --> 00:09:20.140
and kinda explain to you what information
214
00:09:20.140 --> 00:09:22.023
we've got captured here.
215
00:09:23.100 --> 00:09:26.850
So the first column there, the buy-sell indicator,
216
00:09:26.850 --> 00:09:28.530
that's as it relates to the TAS.
217
00:09:28.530 --> 00:09:29.880
So if you see an R,
218
00:09:29.880 --> 00:09:32.490
that represents the requesting agency TAS,
219
00:09:32.490 --> 00:09:35.367
if you see an S, that's servicing agency TAS,
220
00:09:35.367 --> 00:09:37.143
and that's there in column A.
221
00:09:39.150 --> 00:09:42.000
The reciprocal category is captured in column B,
222
00:09:42.000 --> 00:09:44.640
so it'll either be 22, 23, or 24,
223
00:09:44.640 --> 00:09:48.513
which represents that buy-sell reciprocal category.
224
00:09:50.220 --> 00:09:55.220
The GTAS financial statement lines are included in column C,
225
00:09:55.560 --> 00:09:58.863
so that's how you'll see it on the financial statement line.
226
00:10:00.900 --> 00:10:02.850
The sub-element information,
227
00:10:02.850 --> 00:10:05.073
we have that captured in column D,
228
00:10:06.330 --> 00:10:08.747
it categorizes the performance that's involved.
229
00:10:08.747 --> 00:10:12.450
So you will see either a deferred, unreceived,
230
00:10:12.450 --> 00:10:16.470
unsettled, performance, delivered, or easy invoiced.
231
00:10:16.470 --> 00:10:18.960
And we have all of those explained
232
00:10:18.960 --> 00:10:21.330
in more detail down here under the legend.
233
00:10:21.330 --> 00:10:24.180
So I won't really dive into each one of those,
234
00:10:24.180 --> 00:10:26.400
but we do have a legend down at the bottom
235
00:10:26.400 --> 00:10:28.509
that will help you guys understand a little bit
236
00:10:28.509 --> 00:10:30.633
more of what's going on up here.
237
00:10:31.770 --> 00:10:32.820
Can I take a step back?
238
00:10:32.820 --> 00:10:33.653
It looks like what,
239
00:10:33.653 --> 00:10:36.360
and this is Noah Calvin from the State Department,
240
00:10:36.360 --> 00:10:37.470
Sure.
So I see this seems
241
00:10:37.470 --> 00:10:41.700
to be from when I see this report, couple items.
242
00:10:41.700 --> 00:10:43.067
It might be beneficial for any
243
00:10:43.067 --> 00:10:46.920
to have a lot of different TAS, to just have it across.
244
00:10:46.920 --> 00:10:47.880
I've seen other systems
245
00:10:47.880 --> 00:10:49.560
where you have to drill down by a TAS,
246
00:10:49.560 --> 00:10:50.790
that creates a lot more work.
247
00:10:50.790 --> 00:10:53.490
It would be better if there's a global report
248
00:10:53.490 --> 00:10:56.083
that would cover everything just to consider.
249
00:10:56.083 --> 00:11:00.000
The second item is I see this report
250
00:11:00.000 --> 00:11:01.950
and I'm just kind of wondering is there a way
251
00:11:01.950 --> 00:11:05.169
to see what's in GTAS and not in G-Invoicing
252
00:11:05.169 --> 00:11:08.382
or it's only one way where it could see a transaction
253
00:11:08.382 --> 00:11:10.509
that is not in G-Invoicing at all
254
00:11:10.509 --> 00:11:13.890
or is this only it has to be in G-Invoicing?
255
00:11:13.890 --> 00:11:15.840
Just my understanding was just was supposed
256
00:11:15.840 --> 00:11:18.510
to reconcile G-Invoicing to GTAS.
257
00:11:18.510 --> 00:11:19.440
Yes, so
So no.
258
00:11:19.440 --> 00:11:21.210
Good questions there.
259
00:11:21.210 --> 00:11:22.557
Oh, go ahead Alex if you wanna take that.
260
00:11:22.557 --> 00:11:25.010
I can jump in a little bit and help Jeff on that.
261
00:11:25.010 --> 00:11:26.490
So Noah, I know your question as far
262
00:11:26.490 --> 00:11:28.140
as what's in G-Invoicing what's in GTAS.
263
00:11:28.140 --> 00:11:30.171
So when we get further into into this presentation
264
00:11:30.171 --> 00:11:32.307
and talking about the G-Invoicing
265
00:11:32.307 --> 00:11:34.170
and GTAS comparison report,
266
00:11:34.170 --> 00:11:37.139
really on that report it can be more holistic
267
00:11:37.139 --> 00:11:39.360
where you can run it by FR entity in that system,
268
00:11:39.360 --> 00:11:41.970
it's gonna be a more summary level view.
269
00:11:41.970 --> 00:11:43.200
But what Jeff's showing you here
270
00:11:43.200 --> 00:11:45.195
is more the diving in the details of what you're gonna see
271
00:11:45.195 --> 00:11:47.670
in that G-Invoicing and GTAS comparison report.
272
00:11:47.670 --> 00:11:49.590
But I think what your question really led to
273
00:11:49.590 --> 00:11:52.530
was I think the G-Invoicing and GTAS comparison report's
274
00:11:52.530 --> 00:11:53.850
gonna show you you all the data,
275
00:11:53.850 --> 00:11:55.626
you can see both on in that report
276
00:11:55.626 --> 00:11:57.592
what's in G-Invoicing and what's in GTAS
277
00:11:57.592 --> 00:11:59.677
and really dive into those details.
278
00:11:59.677 --> 00:12:02.435
But if you really need to drill down more
279
00:12:02.435 --> 00:12:04.830
on the G-Invoicing information
280
00:12:04.830 --> 00:12:07.020
and drill into a specific TAS,
281
00:12:07.020 --> 00:12:08.910
that's what these G-Invoicing reports are for
282
00:12:08.910 --> 00:12:12.033
to show you what's feeding those specific data points.
283
00:12:14.280 --> 00:12:15.840
Thank you.
284
00:12:15.840 --> 00:12:16.860
You're welcome.
285
00:12:16.860 --> 00:12:18.777
Yep, thanks Alex.
286
00:12:18.777 --> 00:12:19.883
All right, so we'll finish going
287
00:12:19.883 --> 00:12:22.830
across the rows here or the columns here.
288
00:12:22.830 --> 00:12:26.610
So we left off with the sub-element information in column D.
289
00:12:26.610 --> 00:12:29.190
And like I said, we have a little bit more information
290
00:12:29.190 --> 00:12:30.234
about each of those listed down here
291
00:12:30.234 --> 00:12:32.013
under the legend section.
292
00:12:33.300 --> 00:12:35.430
We've got the trading partner, AID in Maine,
293
00:12:35.430 --> 00:12:37.293
listed in columns E and F.
294
00:12:38.970 --> 00:12:40.383
The amount that's in G-Invoicing
295
00:12:40.383 --> 00:12:42.873
will be captured in column G.
296
00:12:45.120 --> 00:12:47.181
The order number or the easy number involved
297
00:12:47.181 --> 00:12:50.070
will be located in column H.
298
00:12:50.070 --> 00:12:54.810
So this report does capture all of the 7,600 easy invoices
299
00:12:54.810 --> 00:12:57.693
as well as the orders, all in this single report.
300
00:12:59.970 --> 00:13:02.610
The trading partner agency group.
301
00:13:02.610 --> 00:13:04.560
The trading partners agency and group names
302
00:13:04.560 --> 00:13:06.780
for both sides, requesting and servicing agencies,
303
00:13:06.780 --> 00:13:09.810
are listed over here in columns I through L.
304
00:13:09.810 --> 00:13:14.010
So that way, you know, just both sides of the equation.
305
00:13:14.010 --> 00:13:17.283
Who's involved in the information here?
306
00:13:18.512 --> 00:13:21.210
So a few things of note with this report,
307
00:13:21.210 --> 00:13:22.043
like I said earlier,
308
00:13:22.043 --> 00:13:24.180
agencies are only able to query one accounting period
309
00:13:24.180 --> 00:13:26.340
and one TAS per report.
310
00:13:26.340 --> 00:13:29.090
And we kind of have that shown in that parameters line.
311
00:13:30.420 --> 00:13:31.500
And I guess the reason behind
312
00:13:31.500 --> 00:13:34.320
allowing only allowing one accounting period in a TAS,
313
00:13:34.320 --> 00:13:36.150
like Alex said, there's really an effort
314
00:13:36.150 --> 00:13:38.730
to really fine tune in on the TAS.
315
00:13:38.730 --> 00:13:42.338
We just had some concerns about the amount of data,
316
00:13:42.338 --> 00:13:44.700
the large volume of data that could be returned
317
00:13:44.700 --> 00:13:48.330
if we were to allow multiples to be pulled.
318
00:13:48.330 --> 00:13:49.950
So for now we're just gonna leave this
319
00:13:49.950 --> 00:13:52.890
as a single accounting period in a single TAS.
320
00:13:52.890 --> 00:13:57.200
So this report is really just kind of designated
321
00:13:57.200 --> 00:13:59.923
or designed to use for really drilling
322
00:13:59.923 --> 00:14:01.863
into one TAS at a time.
323
00:14:02.970 --> 00:14:04.140
Hey Jeff?
324
00:14:04.140 --> 00:14:04.973
Yes.
325
00:14:04.973 --> 00:14:06.780
Before we move on, we have a couple of hands up
326
00:14:06.780 --> 00:14:09.300
that I did want to call on.
327
00:14:09.300 --> 00:14:12.843
So we have Felicia Forward Jones from GSA first.
328
00:14:13.871 --> 00:14:15.240
Good morning.
329
00:14:15.240 --> 00:14:19.260
So when you say that it's limited to one TAS,
330
00:14:19.260 --> 00:14:21.487
that's whoever's pulling the report,
331
00:14:21.487 --> 00:14:26.487
'cause I see multiple TASes within the report itself.
332
00:14:27.780 --> 00:14:32.520
And how does this handle, for example, let's say,
333
00:14:32.520 --> 00:14:36.728
it's a big seller that's pulling this report
334
00:14:36.728 --> 00:14:41.728
and there are, you know, maybe millions of lines
335
00:14:43.876 --> 00:14:46.860
by TAS and document number,
336
00:14:46.860 --> 00:14:49.893
does it then roll over to another tab?
337
00:14:51.570 --> 00:14:53.016
No, that's great question,
338
00:14:53.016 --> 00:14:54.355
and I was just about to get to,
339
00:14:54.355 --> 00:14:56.688
so the note kind of with this is that agencies
340
00:14:56.688 --> 00:14:59.506
can only see the TASes that are associated with the groups
341
00:14:59.506 --> 00:15:03.120
that the TAS reconciler user has access to view.
342
00:15:03.120 --> 00:15:07.860
So the user that logs in as the TAS reconciler
343
00:15:07.860 --> 00:15:09.960
is only gonna pull data for the TAS
344
00:15:09.960 --> 00:15:12.210
and accounting period that they have access to view.
345
00:15:12.210 --> 00:15:14.280
So it's not gonna pull everything,
346
00:15:14.280 --> 00:15:16.555
it's only gonna be kind of in that narrow window
347
00:15:16.555 --> 00:15:18.783
that they have the ability to view.
348
00:15:22.415 --> 00:15:24.360
I dunno if that helps
349
00:15:24.360 --> 00:15:26.410
or if you have additional like questions.
350
00:15:27.840 --> 00:15:30.690
So is it possible to test this
351
00:15:30.690 --> 00:15:35.690
maybe with a user that has a system that may have,
352
00:15:39.240 --> 00:15:42.452
you know, thousands upon thousands of rows?
353
00:15:42.452 --> 00:15:45.903
Has it been tested in that way?
354
00:15:51.060 --> 00:15:52.620
You're expecting it to be at a lower level
355
00:15:52.620 --> 00:15:57.363
that this reconciliation happens?
356
00:15:59.100 --> 00:16:00.980
So Felicia, I think from our perspective
357
00:16:00.980 --> 00:16:03.000
in working with FRB, St Louis,
358
00:16:03.000 --> 00:16:04.620
I'm not aware of any performance issues
359
00:16:04.620 --> 00:16:06.496
as far as like a maximum capacity
360
00:16:06.496 --> 00:16:08.310
for a specific accounting period,
361
00:16:08.310 --> 00:16:11.520
as far as millions of transactions for one specific TAS.
362
00:16:11.520 --> 00:16:15.840
I think we've tried looking at some of the,
363
00:16:15.840 --> 00:16:17.610
especially GSA, I know there's been a seller
364
00:16:17.610 --> 00:16:18.925
has some of those business lines
365
00:16:18.925 --> 00:16:23.925
has huge volumes of activity and we are aware of that
366
00:16:24.387 --> 00:16:26.190
and I'm not aware of any performance issues
367
00:16:26.190 --> 00:16:27.660
from that standpoint.
368
00:16:27.660 --> 00:16:32.660
But as far as the access goes, as far as what Jeff mentioned
369
00:16:33.120 --> 00:16:34.860
and having the correct access
370
00:16:34.860 --> 00:16:37.470
as you're granting access to that TAS reconciler role
371
00:16:37.470 --> 00:16:42.383
and if it's someone that needs a wide range of access
372
00:16:42.383 --> 00:16:46.050
for all the TAS within a certain agency,
373
00:16:46.050 --> 00:16:48.240
I just make sure that they have the correct access
374
00:16:48.240 --> 00:16:49.200
to be able to pull the reports
375
00:16:49.200 --> 00:16:51.573
that are needed to do the reconciliation.
376
00:16:54.900 --> 00:16:56.734
Thank you.
377
00:16:56.734 --> 00:16:58.734
You're welcome.
378
00:17:01.419 --> 00:17:03.300
This is Emily from FRB
379
00:17:03.300 --> 00:17:04.951
and the person just speaking mentioned
380
00:17:04.951 --> 00:17:07.378
that they see multiple TASes.
381
00:17:07.378 --> 00:17:12.117
What Jeff is trying to say, you pull by a single TAS
382
00:17:12.117 --> 00:17:14.129
and if you look up their online five,
383
00:17:14.129 --> 00:17:15.960
that shows the parameter.
384
00:17:15.960 --> 00:17:18.240
So that's the accounting period
385
00:17:18.240 --> 00:17:21.568
and then the exact TAS that was pulled.
386
00:17:21.568 --> 00:17:23.907
So the multiple TASes that you're seeing
387
00:17:23.907 --> 00:17:26.580
are the trading partner TASes.
388
00:17:26.580 --> 00:17:29.250
So that TAS could have been traded
389
00:17:29.250 --> 00:17:32.103
on the other side, the trading partner side,
390
00:17:33.060 --> 00:17:35.850
with, you know, hundreds of TAS.
391
00:17:35.850 --> 00:17:40.170
I have, I've done a lot of testing on this,
392
00:17:40.170 --> 00:17:43.110
our cap is gonna be what the cap is,
393
00:17:43.110 --> 00:17:47.580
and now I can't remember what it is, for Excel.
394
00:17:47.580 --> 00:17:51.063
Like Excel will only let pull so many.
395
00:17:51.960 --> 00:17:55.920
And at this point, I don't have enough performance to hit,
396
00:17:55.920 --> 00:17:58.620
I haven't hit over the cap, let's just say that.
397
00:17:58.620 --> 00:18:00.438
And it pulls relatively quickly.
398
00:18:00.438 --> 00:18:02.077
I can't give you the exact timing,
399
00:18:02.077 --> 00:18:03.960
but I have done some performance
400
00:18:03.960 --> 00:18:06.303
and I've not found any problems with this.
401
00:18:07.230 --> 00:18:09.750
And that's pretty, like to your concern,
402
00:18:09.750 --> 00:18:10.964
is why we limit it to be able
403
00:18:10.964 --> 00:18:13.710
that it has to be the specific TAS,
404
00:18:13.710 --> 00:18:16.320
it's not just like pulling by AID,
405
00:18:16.320 --> 00:18:19.710
because then it really should filter down a lot more.
406
00:18:19.710 --> 00:18:20.766
Like instead of us saying,
407
00:18:20.766 --> 00:18:24.180
"Okay, you can pull by 010 for the AID."
408
00:18:24.180 --> 00:18:25.980
So that's some of, we did put some thought
409
00:18:25.980 --> 00:18:29.760
into not killing anyone's systems
410
00:18:29.760 --> 00:18:31.110
with pulling too much data.
411
00:18:31.110 --> 00:18:33.634
So that's kind of, I just wanted to clarify
412
00:18:33.634 --> 00:18:37.200
like that's why you're seeing multiple TASes
413
00:18:37.200 --> 00:18:40.680
is because you're seeing the partner TAS,
414
00:18:40.680 --> 00:18:44.670
but he really is only pulling by one specific TAS.
415
00:18:44.670 --> 00:18:47.643
I understand but I was just concerned
416
00:18:47.643 --> 00:18:50.790
that some of our larger business lines,
417
00:18:50.790 --> 00:18:54.750
they have one TAS but they tend to do business
418
00:18:54.750 --> 00:18:59.062
with trading partners from all of the different agencies.
419
00:18:59.062 --> 00:18:59.895
Okay.
420
00:18:59.895 --> 00:19:02.850
So by document number in a given month,
421
00:19:02.850 --> 00:19:06.810
that might exceed the lines of Excel.
422
00:19:06.810 --> 00:19:07.800
Okay.
423
00:19:07.800 --> 00:19:08.730
If for example,
424
00:19:08.730 --> 00:19:13.730
we pulled by 047X 4534 001, which is a revolving fund,
425
00:19:15.360 --> 00:19:20.068
which is ASF, just supplies alone I would assume,
426
00:19:20.068 --> 00:19:24.720
with just the supply program within that TAS,
427
00:19:24.720 --> 00:19:26.970
but there other programs that, you know,
428
00:19:26.970 --> 00:19:28.830
Fleet and other programs.
429
00:19:28.830 --> 00:19:29.880
Yeah, sure.
430
00:19:31.020 --> 00:19:34.800
So I can take this back and we can, you know,
431
00:19:34.800 --> 00:19:36.990
it's something we can start to tweak and look into.
432
00:19:36.990 --> 00:19:40.470
It's not, you know, I won't take that off the table.
433
00:19:40.470 --> 00:19:43.519
So it's definitely something we can try to look into
434
00:19:43.519 --> 00:19:46.080
to see if maybe there's a way we can like zip the file.
435
00:19:46.080 --> 00:19:48.150
I mean there could be some other things we could do for this
436
00:19:48.150 --> 00:19:51.990
to make it so you can pull that many and then go from there.
437
00:19:51.990 --> 00:19:54.617
So I wrote that down and I can bring it back
438
00:19:54.617 --> 00:19:57.573
to like our team and we can kind of talk through it.
439
00:19:58.977 --> 00:20:01.737
Thank you.
440
00:20:01.737 --> 00:20:03.592
And Felicia, just this is Alex again,
441
00:20:03.592 --> 00:20:04.740
the only thing I was gonna jump in and say,
442
00:20:04.740 --> 00:20:05.760
you're probably referring
443
00:20:05.760 --> 00:20:08.180
to the acquisition services fund TAS, right?
444
00:20:08.180 --> 00:20:11.490
So I think when, from my experience,
445
00:20:11.490 --> 00:20:15.374
that TAS probably had one of the greatest volume of activity
446
00:20:15.374 --> 00:20:17.643
for cars transactions, I'm guessing.
447
00:20:19.260 --> 00:20:20.160
Right.
448
00:20:21.240 --> 00:20:22.210
So we can definitely take a look.
449
00:20:22.210 --> 00:20:24.971
That's the one, that's the one.
450
00:20:24.971 --> 00:20:26.636
Yep.
451
00:20:26.636 --> 00:20:28.890
And see I think,
I'll get to-
452
00:20:28.890 --> 00:20:32.550
I'm sorry, is that Jeff or Alex?
453
00:20:32.550 --> 00:20:34.050
This is Alex, Bob.
454
00:20:34.050 --> 00:20:34.950
All right.
455
00:20:34.950 --> 00:20:38.807
And see, that was the point I was making in the chat is,
456
00:20:38.807 --> 00:20:42.600
and to Felicia's point, she's spot on.
457
00:20:42.600 --> 00:20:46.800
We have two, three big TASes
458
00:20:46.800 --> 00:20:49.260
where there's a lot of cell activity,
459
00:20:49.260 --> 00:20:51.300
where GSA is the seller,
460
00:20:51.300 --> 00:20:54.450
but we need to have additional filters
461
00:20:54.450 --> 00:20:58.080
that would allow us to grab specific groups,
462
00:20:58.080 --> 00:21:02.267
because the volume is going to be tremendous.
463
00:21:02.267 --> 00:21:06.210
As Felicia spoke on the ASF,
464
00:21:06.210 --> 00:21:09.360
just supply is gonna be tremendous.
465
00:21:09.360 --> 00:21:10.920
And then on the FBF side,
466
00:21:10.920 --> 00:21:13.890
which is a different TAS, it's gonna be rent.
467
00:21:13.890 --> 00:21:16.345
And so we really need to have additional filters
468
00:21:16.345 --> 00:21:17.779
that would enable us
469
00:21:17.779 --> 00:21:21.053
to kind of get a lower number of transactions.
470
00:21:21.053 --> 00:21:26.010
Otherwise, it's gonna be hundreds of thousands of lines
471
00:21:26.010 --> 00:21:27.390
just for one business line.
472
00:21:27.390 --> 00:21:32.010
And if you add 'em all together, it's gonna crash the system
473
00:21:32.010 --> 00:21:33.712
or it's not gonna be able to be accommodated
474
00:21:33.712 --> 00:21:37.720
in Excel or some of the other tools that we use
475
00:21:38.580 --> 00:21:39.413
If that makes sense.
476
00:21:39.413 --> 00:21:40.860
Yeah, so we can look at that, Bob.
477
00:21:40.860 --> 00:21:42.928
So basically, well, I gotta would be
478
00:21:42.928 --> 00:21:46.140
more reporting parameters as far as before you,
479
00:21:46.140 --> 00:21:47.668
the report actually generates versus filtering
480
00:21:47.668 --> 00:21:49.683
and Excel once it's actually there.
481
00:21:51.210 --> 00:21:52.470
And I would add,
482
00:21:52.470 --> 00:21:54.644
I mean I think I asked this question previously
483
00:21:54.644 --> 00:21:57.937
about the status because we're really gonna be interested
484
00:21:57.937 --> 00:22:02.070
in being able to kind of evaluate, you know,
485
00:22:02.070 --> 00:22:07.070
these are maybe in the works or, you know,
486
00:22:07.260 --> 00:22:11.739
sitting with the customer for approval, stuff like that,
487
00:22:11.739 --> 00:22:15.150
because that's all a part of the reconciliation.
488
00:22:15.150 --> 00:22:17.633
We need to be able to see all of the records,
489
00:22:17.633 --> 00:22:22.410
and specifically the status of those records,
490
00:22:22.410 --> 00:22:25.530
because that will help us facilitate kind of looking
491
00:22:25.530 --> 00:22:28.800
at our records within our general ledger and, you know,
492
00:22:28.800 --> 00:22:31.380
look ultimately at the accounting entries
493
00:22:31.380 --> 00:22:35.010
to make sure that at the end of the month, any given month,
494
00:22:35.010 --> 00:22:38.160
that we've made the appropriate entries
495
00:22:38.160 --> 00:22:40.890
for the different activity that we had.
496
00:22:40.890 --> 00:22:42.347
And we fully expect our auditors
497
00:22:42.347 --> 00:22:45.504
wanting to see that type of reconciliation.
498
00:22:45.504 --> 00:22:48.180
So we're trying to be as proactive as we can
499
00:22:48.180 --> 00:22:49.920
to make sure that we're pulling reports,
500
00:22:49.920 --> 00:22:52.200
we're performing reconciliations
501
00:22:52.200 --> 00:22:54.754
between that, what's in G-Invoicing
502
00:22:54.754 --> 00:22:59.100
and what ultimately ends up on our general ledgers.
503
00:22:59.100 --> 00:23:02.610
So we're gonna need essentially all of the records
504
00:23:02.610 --> 00:23:06.090
that were initiated or performed against
505
00:23:06.090 --> 00:23:09.420
or signed or approved during any given month
506
00:23:09.420 --> 00:23:11.250
with the exception of the GT&Cs,
507
00:23:11.250 --> 00:23:14.430
even though I'd still wanna see a list
508
00:23:14.430 --> 00:23:18.621
of all open GT&Cs at any given point in time
509
00:23:18.621 --> 00:23:21.363
if we requested it.
510
00:23:26.822 --> 00:23:28.560
I got you Bob.
511
00:23:28.560 --> 00:23:29.393
That sounds good.
512
00:23:29.393 --> 00:23:30.780
We can definitely take that feedback back
513
00:23:30.780 --> 00:23:32.280
and kind of discuss internally
514
00:23:32.280 --> 00:23:33.810
to see what we could possibly do there
515
00:23:33.810 --> 00:23:36.912
to kind of alleviate some of those issues
516
00:23:36.912 --> 00:23:38.670
you're bringing up.
517
00:23:38.670 --> 00:23:40.120
All right, thank you.
518
00:23:45.690 --> 00:23:47.423
Are there any other questions?
519
00:23:53.520 --> 00:23:55.265
Okay, last thing I'll mention before I turn it over
520
00:23:55.265 --> 00:23:59.390
to, I believe, Justin, I just wanted to call out that
521
00:23:59.390 --> 00:24:02.700
in our most recent publication of the program guide,
522
00:24:02.700 --> 00:24:03.714
we included a new page titled
523
00:24:03.714 --> 00:24:05.521
Business Rules by Reciprocal Category
524
00:24:05.521 --> 00:24:07.740
and it outlines those nine data points
525
00:24:07.740 --> 00:24:10.470
that Alex referenced earlier in the call.
526
00:24:10.470 --> 00:24:12.390
So if there's any questions around that,
527
00:24:12.390 --> 00:24:14.310
I definitely wanted to call out.
528
00:24:14.310 --> 00:24:17.550
We have this document on our G-Invoicing webpage
529
00:24:17.550 --> 00:24:21.390
and I can provide a link in chat once I stop sharing.
530
00:24:21.390 --> 00:24:24.123
But as you scroll down and click this program guide,
531
00:24:25.500 --> 00:24:28.950
we have it in Word and PDF file versions
532
00:24:28.950 --> 00:24:30.690
and it's on the very next to last page.
533
00:24:30.690 --> 00:24:33.123
If you scroll all the way down up one page,
534
00:24:34.230 --> 00:24:39.138
we have the buyer side and seller side business rules
535
00:24:39.138 --> 00:24:40.727
and how we kind of roll these up
536
00:24:40.727 --> 00:24:42.600
into those nine data points.
537
00:24:42.600 --> 00:24:45.300
So just wanted to make sure everybody was aware we had that.
538
00:24:45.300 --> 00:24:47.670
So the combination of the program guide,
539
00:24:47.670 --> 00:24:51.600
the G-Invoicing report, and the ATB summary report
540
00:24:51.600 --> 00:24:52.785
that will be discussed next
541
00:24:52.785 --> 00:24:54.510
will definitely help you guys
542
00:24:54.510 --> 00:24:55.800
in your reconciliation efforts.
543
00:24:55.800 --> 00:24:59.073
So I think that's everything that I had this morning.
544
00:25:05.095 --> 00:25:06.180
Good morning.
545
00:25:06.180 --> 00:25:09.631
That's a good segue to lead into what the demo
546
00:25:09.631 --> 00:25:12.237
that I wanna do with the G-Invoicing
547
00:25:12.237 --> 00:25:14.550
and GTAS comparison report.
548
00:25:14.550 --> 00:25:16.641
Can you guys hear me okay?
549
00:25:16.641 --> 00:25:19.488
Yes, we hear you.
550
00:25:19.488 --> 00:25:20.490
Okay, let me share my screen.
551
00:25:20.490 --> 00:25:23.743
I have just a handful of tabs or a handful of slides here.
552
00:25:28.797 --> 00:25:29.630
Hey Justin,
553
00:25:29.630 --> 00:25:31.350
if you wouldn't mind just speaking a little louder,
554
00:25:31.350 --> 00:25:32.790
coming in a little low.
555
00:25:32.790 --> 00:25:34.353
Okay, will do.
556
00:25:36.664 --> 00:25:38.564
Can you see the slides I'm presenting?
557
00:25:42.780 --> 00:25:44.580
Yes, I can see the slides.
558
00:25:44.580 --> 00:25:45.990
Okay, thanks.
559
00:25:45.990 --> 00:25:49.166
So yeah, this, like I said, that's a good segue for Jeff.
560
00:25:49.166 --> 00:25:52.140
You know, and here's a high level of the nine data points
561
00:25:52.140 --> 00:25:55.770
that the G-Invoicing GTAS comparison report.
562
00:25:55.770 --> 00:25:59.013
We'll be looking at over on the GTAS side of the house.
563
00:26:00.090 --> 00:26:04.800
So you can reach out to us directly to GTAS team or Jeff
564
00:26:04.800 --> 00:26:07.315
or the G-Invoicing website to get further details
565
00:26:07.315 --> 00:26:09.303
on these nine data points.
566
00:26:12.180 --> 00:26:16.060
GTAS currently has proposed analytical edits
567
00:26:17.550 --> 00:26:20.220
to compare the GTAS data and the G-Invoicing data.
568
00:26:20.220 --> 00:26:24.060
These are edits 184 through 191
569
00:26:24.060 --> 00:26:25.590
and here's quick screenshots
570
00:26:25.590 --> 00:26:29.103
to kind of gives a high level view of what those edits are.
571
00:26:31.119 --> 00:26:33.120
This is, like Alex had mentioned,
572
00:26:33.120 --> 00:26:34.470
this will ultimately be used as a metric
573
00:26:34.470 --> 00:26:36.990
on the scorecard for significant entities.
574
00:26:36.990 --> 00:26:39.720
They are still currently proposed analytical
575
00:26:39.720 --> 00:26:42.120
and will not cause the bulk file to fail.
576
00:26:42.120 --> 00:26:43.590
It's just providing data for physical
577
00:26:43.590 --> 00:26:45.930
and the government market needed to reconcile
578
00:26:45.930 --> 00:26:48.230
and may eventually become fatal in the future.
579
00:26:49.410 --> 00:26:52.260
And I will provide a couple links
580
00:26:52.260 --> 00:26:53.490
that gives you more information
581
00:26:53.490 --> 00:26:56.670
out on our Fiscal Service webpage
582
00:26:56.670 --> 00:26:59.273
and I'll provide that in the chat here in just a second.
583
00:27:00.750 --> 00:27:02.973
So generating the report in GTAS.
584
00:27:03.870 --> 00:27:07.950
This is a screenshot of the GTAS reports module.
585
00:27:07.950 --> 00:27:09.740
Pretty straightforward.
586
00:27:09.740 --> 00:27:13.380
The report will be located in the reports module
587
00:27:13.380 --> 00:27:15.723
under the intergovernmental report type.
588
00:27:16.800 --> 00:27:17.640
You would run it by the screen.
589
00:27:17.640 --> 00:27:18.786
Can you speak up a little bit please?
590
00:27:18.786 --> 00:27:20.970
It's still hard to hear you.
591
00:27:20.970 --> 00:27:22.380
Okay, sorry, no.
592
00:27:22.380 --> 00:27:27.380
Yeah, so this is the module for the GTAS report module.
593
00:27:28.590 --> 00:27:31.347
So to get the report out of GTAS,
594
00:27:31.347 --> 00:27:32.480
you would ultimately go
595
00:27:32.480 --> 00:27:35.310
to the intergovernmental report type,
596
00:27:35.310 --> 00:27:37.983
run the parameters that you are needing.
597
00:27:38.850 --> 00:27:42.081
You would run it by period, ATB solution status,
598
00:27:42.081 --> 00:27:45.180
and run by FR entity, you would choose
599
00:27:45.180 --> 00:27:48.063
or select your FR entity and run the report.
600
00:27:49.710 --> 00:27:52.167
Oh, excuse me, I'm sorry,
601
00:27:52.167 --> 00:27:54.873
I'm really having difficulty hearing.
602
00:27:55.770 --> 00:27:59.262
It's, I don't know, it's kind of like in and out,
603
00:27:59.262 --> 00:28:02.433
like your voice is fading at some point.
604
00:28:04.188 --> 00:28:06.940
Gimme one sec, lemme check the mic.
605
00:28:06.940 --> 00:28:08.451
The mic volume.
606
00:28:08.451 --> 00:28:10.240
Thank you, I'm sorry.
607
00:28:10.240 --> 00:28:11.073
I'm not sure that that's on your end,
608
00:28:11.073 --> 00:28:14.253
because I'm not getting the cut out over here.
609
00:28:15.240 --> 00:28:17.040
Headphones may help as well.
610
00:28:17.040 --> 00:28:18.813
It's some background noise.
611
00:28:19.950 --> 00:28:21.210
Yeah, we're hearing some,
612
00:28:21.210 --> 00:28:22.384
there's like some fan sound
613
00:28:22.384 --> 00:28:25.980
or some wind type noise in the background.
614
00:28:25.980 --> 00:28:28.080
I think if you could put a headset on perhaps,
615
00:28:28.080 --> 00:28:30.280
that would help, or dial in with your phone.
616
00:28:34.813 --> 00:28:36.563
Sorry, yeah, give me one second here.
617
00:28:49.389 --> 00:28:51.139
Is that better there?
618
00:28:52.830 --> 00:28:53.663
Yes, a bit.
619
00:28:53.663 --> 00:28:54.663
Thank you very much.
620
00:28:56.880 --> 00:28:57.810
Sure.
621
00:28:57.810 --> 00:28:59.753
Okay, so let me share my screen
622
00:28:59.753 --> 00:29:01.863
with the actual report itself.
623
00:29:06.960 --> 00:29:07.923
Give me one second.
624
00:29:16.230 --> 00:29:18.590
Can you see the report that's generated on GTAS
625
00:29:18.590 --> 00:29:19.743
in Excel format?
626
00:29:23.370 --> 00:29:25.440
Yep, we can see it Justin.
627
00:29:25.440 --> 00:29:26.603
Okay, thank you.
628
00:29:30.067 --> 00:29:32.520
So as you can see, there's multiple tabs
629
00:29:32.520 --> 00:29:35.333
on the new formatted report that you can generate out
630
00:29:35.333 --> 00:29:39.646
on GTAS for the GTAS invoice and comparison report.
631
00:29:39.646 --> 00:29:41.463
The first one is the combined,
632
00:29:42.793 --> 00:29:47.793
it has both GTAS and G-Invoicing breakout data.
633
00:29:48.780 --> 00:29:50.670
You have a combined amount
634
00:29:50.670 --> 00:29:54.450
and you included both the GTAS side
635
00:29:54.450 --> 00:29:55.890
and the data that we interface over
636
00:29:55.890 --> 00:29:57.660
from the G-invoicing side.
637
00:29:57.660 --> 00:30:00.620
And you're able to compare the differences here
638
00:30:00.620 --> 00:30:02.749
on this high level summary tab.
639
00:30:02.749 --> 00:30:06.660
As you can see over here in columns A and B,
640
00:30:06.660 --> 00:30:09.990
the GTAS statement number and the G-Invoicing breakout data
641
00:30:09.990 --> 00:30:14.990
has linked lines to where you can dive into the details
642
00:30:15.720 --> 00:30:17.280
of the data in the sum line
643
00:30:17.280 --> 00:30:20.853
that's presented here on this combined summary tab.
644
00:30:21.840 --> 00:30:23.940
It's similar to reclassified statements
645
00:30:23.940 --> 00:30:25.713
that are generated out of GTAS.
646
00:30:27.114 --> 00:30:30.900
They've recently included a breakout
647
00:30:30.900 --> 00:30:34.473
of interdepartmental data versus intradepartmental data.
648
00:30:35.520 --> 00:30:40.140
So this data here, interdepartmentals, obviously it is,
649
00:30:40.140 --> 00:30:45.140
you know, data that's training within itself an FR entity.
650
00:30:46.440 --> 00:30:49.080
So it's a different way to break down the data
651
00:30:49.080 --> 00:30:52.113
of what is internal versus what is interdepartmental
652
00:30:52.113 --> 00:30:53.943
with the government-wide community.
653
00:30:55.890 --> 00:30:58.620
Same goes for the interdepartmental tabs.
654
00:30:58.620 --> 00:31:02.820
They're linked and you can click on each link
655
00:31:02.820 --> 00:31:04.380
whether you want to dive into the details
656
00:31:04.380 --> 00:31:06.819
of what's coming over from G-Invoicing
657
00:31:06.819 --> 00:31:11.819
or what has been submitted on the bulk file via GTAS.
658
00:31:11.970 --> 00:31:16.500
So for a quick example, if you wanted to look at line 3.4,
659
00:31:16.500 --> 00:31:19.860
we just click on line 3.4
660
00:31:19.860 --> 00:31:22.170
and this will give you the breakout of the bulk file
661
00:31:22.170 --> 00:31:23.699
that makes up that summary line
662
00:31:23.699 --> 00:31:26.823
or that total line for that line amount.
663
00:31:30.690 --> 00:31:33.060
The following tabs here, the GTAS bulk file,
664
00:31:33.060 --> 00:31:35.820
this is accumulation of the entire bulk file data
665
00:31:35.820 --> 00:31:37.470
that is used in the report.
666
00:31:37.470 --> 00:31:39.600
Like Noah was was asking about,
667
00:31:39.600 --> 00:31:43.440
this will give you some avenues to dive deeper into the data
668
00:31:43.440 --> 00:31:46.260
of what is on the bulk file itself
669
00:31:46.260 --> 00:31:49.160
versus what is being poured over from the G-Invoicing side
670
00:31:50.190 --> 00:31:53.553
that you can see here on this tab as well.
671
00:32:01.793 --> 00:32:03.603
The individual lines here,
672
00:32:07.451 --> 00:32:11.370
you can go through the line analysis and provide,
673
00:32:11.370 --> 00:32:14.130
it gives you a tool you can utilize
674
00:32:14.130 --> 00:32:16.980
as you're doing the reconciliation process.
675
00:32:16.980 --> 00:32:19.050
Additionally, you'll have the details
676
00:32:19.050 --> 00:32:21.750
of the proposed analytical edits
677
00:32:21.750 --> 00:32:23.040
that will provide the differences
678
00:32:23.040 --> 00:32:27.329
that are occurring between the statement line
679
00:32:27.329 --> 00:32:28.983
and the G-Invoicing data.
680
00:32:36.540 --> 00:32:40.620
In general, that's a high level view of the report itself.
681
00:32:40.620 --> 00:32:45.018
I know it was a quick demonstration, pretty self-explanatory
682
00:32:45.018 --> 00:32:49.770
and provides adequate details to reconcile
683
00:32:49.770 --> 00:32:53.433
as we continue with our effort between GTAS and G-Invoicing.
684
00:32:55.110 --> 00:32:56.523
Additionally at year-end-
685
00:32:57.480 --> 00:32:58.590
Hey Justin, do you wanna go back
686
00:32:58.590 --> 00:33:00.982
to maybe one of the first three tabs real quick?
687
00:33:00.982 --> 00:33:01.815
Sure.
688
00:33:01.815 --> 00:33:04.260
I think it might be helpful to point out the legend.
689
00:33:04.260 --> 00:33:05.940
This is Sue from St. Louis FRB.
690
00:33:05.940 --> 00:33:07.940
When we were creating this report,
691
00:33:07.940 --> 00:33:10.196
we work closely with the G-Invoicing team
692
00:33:10.196 --> 00:33:11.847
and we were getting feedback from agencies
693
00:33:11.847 --> 00:33:13.230
and we wanted to make sure
694
00:33:13.230 --> 00:33:15.813
that we know some of the users for this report
695
00:33:15.813 --> 00:33:18.017
will be familiar with GTAS but some will not.
696
00:33:18.017 --> 00:33:21.900
And so we wanted to make sure that the legends were helpful.
697
00:33:21.900 --> 00:33:24.070
So that's, you know, like a fiscal period in GTAS
698
00:33:24.070 --> 00:33:26.703
is an accounting period in G-Invoicing for example.
699
00:33:27.690 --> 00:33:29.850
So we wanted to make sure that the column headers make sense
700
00:33:29.850 --> 00:33:31.530
so you understand what data you're looking at.
701
00:33:31.530 --> 00:33:32.730
So I just thought it would be, you know,
702
00:33:32.730 --> 00:33:34.189
might be helpful for users not familiar
703
00:33:34.189 --> 00:33:37.290
with re-classified financial statement reports
704
00:33:37.290 --> 00:33:40.230
to look at that just to make sure that, you know,
705
00:33:40.230 --> 00:33:43.620
they can easily identify the data that they're looking at.
706
00:33:43.620 --> 00:33:48.620
And just for a review, the manual adjustments being reported
707
00:33:49.050 --> 00:33:51.500
as interdepartmental versus intradepartmental,
708
00:33:51.500 --> 00:33:55.650
that's a new concept within GTAS from last year.
709
00:33:55.650 --> 00:33:58.888
And so that's why we have three tabs breaking out this data,
710
00:33:58.888 --> 00:34:00.780
because we wanted to make sure
711
00:34:00.780 --> 00:34:03.731
that anything that was easily identifiable
712
00:34:03.731 --> 00:34:07.230
is intradepartmental versus interdepartmental
713
00:34:07.230 --> 00:34:08.763
was displayed here.
714
00:34:16.260 --> 00:34:17.093
Thank you Sue.
715
00:34:17.093 --> 00:34:18.630
Yeah, if you want to elaborate a little bit
716
00:34:18.630 --> 00:34:20.637
on the manual adjustment data
717
00:34:20.637 --> 00:34:25.500
that will be presented in the period 12 report as well
718
00:34:25.500 --> 00:34:26.340
if you don't mind.
719
00:34:26.340 --> 00:34:27.420
Yeah, sure.
720
00:34:27.420 --> 00:34:31.980
Yeah, so manual adjustments are only for period 12.
721
00:34:31.980 --> 00:34:33.330
So the column here,
722
00:34:33.330 --> 00:34:36.360
obviously this is a report run for period three,
723
00:34:36.360 --> 00:34:38.100
so you're not seeing any manual adjustments,
724
00:34:38.100 --> 00:34:39.870
but when it is available,
725
00:34:39.870 --> 00:34:44.190
these first three tabs will have that additional information
726
00:34:44.190 --> 00:34:47.160
so you'll know what the manual adjustment amount was
727
00:34:47.160 --> 00:34:51.030
for like a combined amount and then it will break it out
728
00:34:51.030 --> 00:34:53.700
versus intradepartmental or interdepartmental
729
00:34:53.700 --> 00:34:56.700
depending on if the agency is using itself
730
00:34:56.700 --> 00:34:58.833
as a trading partner or not.
731
00:35:00.750 --> 00:35:03.300
We do have, just as a reminder,
732
00:35:03.300 --> 00:35:08.300
this data for this first year is gonna be filtered on a TAS,
733
00:35:08.340 --> 00:35:13.340
that's a BPOA of 2023, to help with the mandate,
734
00:35:13.860 --> 00:35:16.560
'cause that's really the only TAS data
735
00:35:16.560 --> 00:35:18.963
that's of interest during this first year.
736
00:35:20.040 --> 00:35:22.650
And to further help with manual adjustments,
737
00:35:22.650 --> 00:35:24.960
we do have a coming soon feature
738
00:35:24.960 --> 00:35:28.380
that'll be part of our year-end release.
739
00:35:28.380 --> 00:35:31.380
We'll have a new tab called manual adjustments
740
00:35:31.380 --> 00:35:34.920
and it'll be a culmination of all manual adjustments
741
00:35:34.920 --> 00:35:39.180
broken out for their USSGL account number
742
00:35:39.180 --> 00:35:41.070
and trading partner FR entity.
743
00:35:41.070 --> 00:35:43.010
I do have a mock-up of that,
744
00:35:43.010 --> 00:35:44.860
if I could just show that real quick.
745
00:35:46.590 --> 00:35:47.970
So this will be coming soon
746
00:35:47.970 --> 00:35:51.633
so you'll have a new tab for manual adjustments.
747
00:35:52.800 --> 00:35:55.020
There was a request to include this
748
00:35:55.020 --> 00:35:57.120
so it does have a nice breakout
749
00:35:57.120 --> 00:35:58.440
of all the manual adjustments
750
00:35:58.440 --> 00:36:02.170
and you can easily see which USSGL account number
751
00:36:02.170 --> 00:36:05.310
and additionally the trading partner FR entity
752
00:36:05.310 --> 00:36:07.380
and it'll just be all in one place.
753
00:36:07.380 --> 00:36:08.977
So instead of it being broken out across all the tabs,
754
00:36:08.977 --> 00:36:11.163
you'll see it right here.
755
00:36:12.990 --> 00:36:13.875
And then the other request
756
00:36:13.875 --> 00:36:16.353
was to include the trading partner FR entity
757
00:36:16.353 --> 00:36:18.840
across all the statement tabs.
758
00:36:18.840 --> 00:36:21.603
So like Justin was pointing out, all the different data,
759
00:36:21.603 --> 00:36:24.390
there's just a different data table on each tab
760
00:36:24.390 --> 00:36:26.990
that will also include in trading partner FR entity.
761
00:36:38.820 --> 00:36:40.530
Okay, yep.
762
00:36:40.530 --> 00:36:42.810
We do have a couple of questions in chat
763
00:36:42.810 --> 00:36:45.060
that I did want to call out.
764
00:36:45.060 --> 00:36:46.950
Been sitting on them for a few moments,
765
00:36:46.950 --> 00:36:50.070
but just need a confirmation.
766
00:36:50.070 --> 00:36:53.790
Justin, this one was from Susan Walton at FEMA.
767
00:36:53.790 --> 00:36:56.010
She wanted to know if the reporting
768
00:36:56.010 --> 00:36:59.343
only includes reciprocal categories 22, 23, and 24?
769
00:37:01.470 --> 00:37:02.940
Hey Robert, this is Alex, I can take that.
770
00:37:02.940 --> 00:37:05.340
Yes Susan, so any of the activity
771
00:37:05.340 --> 00:37:07.350
that's being passed over by state line
772
00:37:07.350 --> 00:37:09.497
are only those by cell reciprocal categories
773
00:37:09.497 --> 00:37:13.413
of 22, 23, and 24 that we're comparing.
774
00:37:16.710 --> 00:37:17.543
Thank you Alex.
775
00:37:17.543 --> 00:37:21.720
And then we had another question from Catherine Kulfis.
776
00:37:21.720 --> 00:37:23.100
What would the combined
777
00:37:23.100 --> 00:37:25.743
comparison differences consist of?
778
00:37:30.870 --> 00:37:32.490
So Catherine, I believe on that,
779
00:37:32.490 --> 00:37:33.600
and Sue correct me if I'm wrong,
780
00:37:33.600 --> 00:37:35.610
I believe the combined is a combination
781
00:37:35.610 --> 00:37:38.100
of both the intra and interdepartmental tabs
782
00:37:38.100 --> 00:37:41.010
to all be on long tab versus having them split out.
783
00:37:41.010 --> 00:37:43.020
So I think those two are just combined on that.
784
00:37:43.020 --> 00:37:44.310
But Sue correct me if I'm wrong.
785
00:37:44.310 --> 00:37:46.140
Right, no, that's absolutely correct.
786
00:37:46.140 --> 00:37:46.973
Yep.
787
00:37:53.070 --> 00:37:54.930
Okay, so I think that catches us up
788
00:37:54.930 --> 00:37:57.513
on our outstanding chat questions.
789
00:37:59.070 --> 00:38:03.060
So what we can do is just open up the floor
790
00:38:03.060 --> 00:38:05.468
for any additional questions
791
00:38:05.468 --> 00:38:07.654
or maybe if there's anything that you wanna see
792
00:38:07.654 --> 00:38:09.420
on the G-Invoicing side,
793
00:38:09.420 --> 00:38:10.950
now would be a good time to ask that as well.
794
00:38:10.950 --> 00:38:13.953
We can certainly go back to that portion and answer that.
795
00:38:19.560 --> 00:38:23.100
All right, got a question from Rom at FAA,
796
00:38:23.100 --> 00:38:25.320
will there be APA, excuse me,
797
00:38:25.320 --> 00:38:27.623
will there be API support so data can be pulled
798
00:38:27.623 --> 00:38:32.163
into financial systems for reconciliation and research?
799
00:38:37.740 --> 00:38:42.740
So Rom, I can answer this from the G-Invoicing perspective
800
00:38:43.770 --> 00:38:47.190
and, you know, it may be a similar answer from GTAS.
801
00:38:47.190 --> 00:38:48.540
So our initial offering
802
00:38:48.540 --> 00:38:53.540
is certainly through the user interface
803
00:38:54.451 --> 00:38:58.440
and these Excel-based reports.
804
00:38:58.440 --> 00:39:02.610
We don't currently have plans to offer this via API,
805
00:39:02.610 --> 00:39:04.293
but, you know, if there are enough agencies
806
00:39:04.293 --> 00:39:06.420
that have an interest in that,
807
00:39:06.420 --> 00:39:08.813
it's certainly something that can be considered.
808
00:39:13.650 --> 00:39:15.570
And Rom, I know from the the GTAS protective,
809
00:39:15.570 --> 00:39:17.148
I know there's not really API connections
810
00:39:17.148 --> 00:39:20.610
set up to run reports out of like the actual system there.
811
00:39:20.610 --> 00:39:22.410
So I know that's not currently.
812
00:39:22.410 --> 00:39:24.690
Users have to log in to pull those reports out
813
00:39:24.690 --> 00:39:26.430
and there's not a API connection
814
00:39:26.430 --> 00:39:28.916
for any of those GTAS reports
815
00:39:28.916 --> 00:39:30.873
for external agencies currently.
816
00:39:36.066 --> 00:39:38.250
Okay, I see there's a couple of hands up
817
00:39:38.250 --> 00:39:40.181
and I'll get to you here in a moment.
818
00:39:40.181 --> 00:39:41.893
I just wanna address one more in chat
819
00:39:41.893 --> 00:39:43.983
and then I'll switch over to you Lisa.
820
00:39:45.150 --> 00:39:50.150
So how long is ODNI exempt from using G-Invoicing?
821
00:39:50.703 --> 00:39:54.843
So I just want to clarify there, ODNI is not exempt,
822
00:39:56.040 --> 00:39:59.070
they're just delayed in implementing G-Invoicing
823
00:39:59.070 --> 00:40:04.070
and we're hoping that sometime here in the near future,
824
00:40:04.620 --> 00:40:06.870
we'll be able to share their plans
825
00:40:06.870 --> 00:40:08.959
in terms of how they're planning on to implement
826
00:40:08.959 --> 00:40:11.130
and come into G-Invoicing.
827
00:40:11.130 --> 00:40:13.670
They're really close with their technical solution
828
00:40:13.670 --> 00:40:16.230
and their plan for implementation.
829
00:40:16.230 --> 00:40:17.894
So hopefully we'll have some details
830
00:40:17.894 --> 00:40:20.343
that'll be shareable here in the near future.
831
00:40:22.530 --> 00:40:23.670
Okay.
832
00:40:23.670 --> 00:40:25.350
I know we got a couple more questions Robert,
833
00:40:25.350 --> 00:40:27.033
I know I think Rebecca asked,
834
00:40:28.110 --> 00:40:29.640
the comparison is not expected down
835
00:40:29.640 --> 00:40:32.490
to the TAS sub-account level, correct?
836
00:40:32.490 --> 00:40:37.490
So Rebecca on that, I guess any unique TAS
837
00:40:39.990 --> 00:40:41.817
will be shown on the report.
838
00:40:41.817 --> 00:40:44.550
And just to like, I guess make sure everyone's aware,
839
00:40:44.550 --> 00:40:46.470
this isn't like a required reconciliation
840
00:40:46.470 --> 00:40:48.600
that Treasury's requiring that you do,
841
00:40:48.600 --> 00:40:50.970
it's really more of a tool we're trying to put in place
842
00:40:50.970 --> 00:40:54.090
to help you reconcile any data
843
00:40:54.090 --> 00:40:56.640
between your data that's being reported in GTAS
844
00:40:56.640 --> 00:40:58.454
and what's being transacted in G-Invoicing
845
00:40:58.454 --> 00:41:03.000
to kind of identify where the gaps are in that reporting
846
00:41:03.000 --> 00:41:05.490
so you can improve your overall score
847
00:41:05.490 --> 00:41:07.763
that is being displayed on your scorecard, so.
848
00:41:07.763 --> 00:41:10.215
But we will give all the data that is being reported in GTAS
849
00:41:10.215 --> 00:41:13.035
and data that's being passed across from G-Invoicing
850
00:41:13.035 --> 00:41:15.783
and have that down to that unique TAS level.
851
00:41:18.210 --> 00:41:22.050
The next question I see Robert, is I think from Scott Young.
852
00:41:22.050 --> 00:41:23.400
Will there be any timing differences
853
00:41:23.400 --> 00:41:26.460
between G-Invoicing in cars or records
854
00:41:26.460 --> 00:41:30.270
or are the records updated real time in both systems?
855
00:41:30.270 --> 00:41:31.890
So Scott, on that,
856
00:41:31.890 --> 00:41:33.930
I think it was a question we had previously in the chat,
857
00:41:33.930 --> 00:41:37.710
so the GTAS reporting's always done,
858
00:41:37.710 --> 00:41:40.485
like so the March GTAS reportings happens in April.
859
00:41:40.485 --> 00:41:43.890
So there's really a delay there
860
00:41:43.890 --> 00:41:46.058
of when the GTAS reporting actually happens.
861
00:41:46.058 --> 00:41:48.692
So I believe for G-Invoicing,
862
00:41:48.692 --> 00:41:51.300
the period has three business days
863
00:41:51.300 --> 00:41:54.150
after the close of the month,
864
00:41:54.150 --> 00:41:56.550
so you have three business days to do that.
865
00:41:56.550 --> 00:41:59.620
And with GTAS, the GTAS reporting doesn't open up
866
00:41:59.620 --> 00:42:01.470
until the fourth business day.
867
00:42:01.470 --> 00:42:06.060
So we interface in the G-Invoicing information in the GTAS
868
00:42:06.060 --> 00:42:09.790
before the opening of the GTAS reporting window.
869
00:42:09.790 --> 00:42:12.957
So the information that's being pulled from G-Invoicing
870
00:42:12.957 --> 00:42:16.920
and GTAS should be finalized as that point for March,
871
00:42:16.920 --> 00:42:18.330
because there's no changes that can happen
872
00:42:18.330 --> 00:42:19.830
after that third business day.
873
00:42:23.250 --> 00:42:25.260
And I see one more question and I think from DOJ,
874
00:42:25.260 --> 00:42:27.960
can the data be downloaded like an ATB?
875
00:42:27.960 --> 00:42:31.020
Yes, the data, like Justin was showing in the reports model,
876
00:42:31.020 --> 00:42:33.022
the data can be downloaded into Excel format
877
00:42:33.022 --> 00:42:34.770
that Justin was shown, but yes,
878
00:42:34.770 --> 00:42:38.223
it can be downloaded from GTAS from the reports module.
879
00:42:42.930 --> 00:42:43.890
Thanks Alex.
880
00:42:43.890 --> 00:42:46.680
Okay, I'm going to switch to the hands that are up now.
881
00:42:46.680 --> 00:42:48.993
So Lisa Deger, you're up first.
882
00:42:50.040 --> 00:42:51.930
Good morning.
883
00:42:51.930 --> 00:42:54.180
I'm bet Alex and Justin and Wes
884
00:42:54.180 --> 00:42:56.640
are probably gonna guess what I'm gonna say.
885
00:42:56.640 --> 00:43:01.640
And that is that until G-Invoicing and GTAS
886
00:43:02.040 --> 00:43:06.733
can include our limits or SAHIs, AID97 and 17,
887
00:43:10.200 --> 00:43:13.540
are gonna have a very difficult time with reconciliations
888
00:43:13.540 --> 00:43:16.563
with our trading partners and between our data.
889
00:43:17.580 --> 00:43:22.530
So I know that there is a generic field
890
00:43:22.530 --> 00:43:25.440
in the G-Invoicing that we're going to be using.
891
00:43:25.440 --> 00:43:27.993
I can't tell you what that is offhand,
892
00:43:28.890 --> 00:43:32.777
but I don't think it will be included
893
00:43:32.777 --> 00:43:35.610
in the G-Invoicing report.
894
00:43:35.610 --> 00:43:38.156
And certainly if it isn't in GTAS,
895
00:43:38.156 --> 00:43:40.288
then we'll only have half the answer
896
00:43:40.288 --> 00:43:42.990
if we ever get it in G-Invoicing.
897
00:43:42.990 --> 00:43:46.410
So I would be remiss if I didn't take the opportunity
898
00:43:46.410 --> 00:43:47.523
to mention that again.
899
00:43:48.570 --> 00:43:49.403
Thanks.
900
00:43:49.403 --> 00:43:50.236
Yep, yep.
901
00:43:50.236 --> 00:43:52.103
I definitely appreciate the feedback on that Lisa
902
00:43:52.103 --> 00:43:54.660
and we can take that back internally just take a look at it
903
00:43:54.660 --> 00:43:57.420
and see how we can best help out with that.
904
00:43:57.420 --> 00:43:59.468
But yeah, we understand that is an issue,
905
00:43:59.468 --> 00:44:02.963
until we get that addressed both from the DOD side
906
00:44:02.963 --> 00:44:04.260
and the Treasury side.
907
00:44:04.260 --> 00:44:05.610
So we can take that back
908
00:44:05.610 --> 00:44:07.470
and then if we need to have further conversations around it,
909
00:44:07.470 --> 00:44:08.670
we can definitely do so.
910
00:44:11.307 --> 00:44:14.326
All right, thank you Lisa and Alex.
911
00:44:14.326 --> 00:44:17.562
This is Angela NRC again,
912
00:44:17.562 --> 00:44:22.562
I did not understand what that was really about.
913
00:44:22.680 --> 00:44:25.113
Can you expand a little bit please?
914
00:44:26.550 --> 00:44:29.700
Angela, are you talking about on the DOD question?
915
00:44:29.700 --> 00:44:31.082
Yes, please.
916
00:44:31.082 --> 00:44:33.450
It's more of an internal DOD issue,
917
00:44:33.450 --> 00:44:35.070
it's not a government wide issue.
918
00:44:35.070 --> 00:44:37.950
It happens to do with their SAHI in their internal systems
919
00:44:37.950 --> 00:44:41.010
and being able to reconcile back between the two systems.
920
00:44:41.010 --> 00:44:41.846
But it's really not a issue
921
00:44:41.846 --> 00:44:44.610
that's widespread across the government,
922
00:44:44.610 --> 00:44:45.841
it's more internal to DOD.
923
00:44:45.841 --> 00:44:47.495
But Lisa, correct me wrong, do you want me to do that?
924
00:44:47.495 --> 00:44:50.078
Yeah, I would say that
925
00:44:51.450 --> 00:44:56.450
it is an internal structure to DOD, but it is an issue.
926
00:44:57.180 --> 00:45:00.480
The 97 agencies of which there are, I dunno,
927
00:45:00.480 --> 00:45:05.480
35 to 40 of them, under 97 each have a specific identifier,
928
00:45:07.050 --> 00:45:11.460
which we would call a SAHI sub-account holder,
929
00:45:11.460 --> 00:45:14.250
indicator, or a limitation.
930
00:45:14.250 --> 00:45:18.835
And each limit or SAHI indicates which trading partner,
931
00:45:18.835 --> 00:45:21.870
which defense agency you're doing business with.
932
00:45:21.870 --> 00:45:26.870
We have shared main accounts, 0100, 0300, 0500, 0400,
933
00:45:29.910 --> 00:45:34.910
so we had got shared main accounts, we've got a shared AID,
934
00:45:36.600 --> 00:45:40.100
but we've got 30 plus agencies under the 97.
935
00:45:40.100 --> 00:45:44.940
And so the reconciliation for us
936
00:45:44.940 --> 00:45:47.493
would need to be at the defense agency level,
937
00:45:48.690 --> 00:45:50.853
not the main account.
938
00:45:53.490 --> 00:45:55.320
I mean, we can reconcile a main account, right?
939
00:45:55.320 --> 00:45:59.550
But I can't tell you which defense agency
940
00:45:59.550 --> 00:46:01.233
you would be doing business with.
941
00:46:03.735 --> 00:46:05.284
Okay, so it's at the higher level
942
00:46:05.284 --> 00:46:10.284
that NRC would be reconciling with not at that sub agency?
943
00:46:10.948 --> 00:46:12.335
I think it's at a lower level.
944
00:46:12.335 --> 00:46:17.335
I think we are at a lower level, we have sub-accounts,
945
00:46:18.720 --> 00:46:23.720
but I mean it's the next, I would call it the next step down
946
00:46:26.160 --> 00:46:28.770
that helps us, say, whether you're doing business
947
00:46:28.770 --> 00:46:30.534
with Missile Defense Agency,
948
00:46:30.534 --> 00:46:35.534
or can file, or I mean all of them.
949
00:46:36.480 --> 00:46:38.238
Yeah, Angela, it really gets to the fact
950
00:46:38.238 --> 00:46:43.151
that a number of agencies share AIGs
951
00:46:43.151 --> 00:46:48.097
and these are identifiers that DOD uses to make
952
00:46:49.560 --> 00:46:52.113
or to delineate the activity.
953
00:46:53.760 --> 00:46:55.140
So, you know, which defense agency
954
00:46:55.140 --> 00:46:56.940
is actually executing that work
955
00:46:56.940 --> 00:46:59.403
under the 0970 AID for instance.
956
00:47:02.790 --> 00:47:03.623
Okay.
957
00:47:03.623 --> 00:47:04.590
I have business
958
00:47:04.590 --> 00:47:08.373
with Air Force for US transcom right now.
959
00:47:10.470 --> 00:47:11.853
Am I gonna have an issue?
960
00:47:12.960 --> 00:47:16.890
If you work the 57th side of Air Force?
961
00:47:16.890 --> 00:47:21.733
But I believe transcom has some under 97.
962
00:47:23.400 --> 00:47:26.280
Okay, so that's what sparked my
963
00:47:26.280 --> 00:47:28.333
or piqued my interest, right?
964
00:47:28.333 --> 00:47:29.219
Right.
965
00:47:29.219 --> 00:47:31.260
When you said 97 and 17,
966
00:47:31.260 --> 00:47:33.270
I'm like, "Ours?"
967
00:47:33.270 --> 00:47:34.260
So.
968
00:47:34.260 --> 00:47:35.781
Yeah, 97.
969
00:47:35.781 --> 00:47:38.323
Well yeah, 57's Air Force, so that shouldn't be.
970
00:47:38.323 --> 00:47:40.530
But you will for transcom.
971
00:47:40.530 --> 00:47:43.560
You would have, yes.
972
00:47:43.560 --> 00:47:47.663
17 is Navy being, they have subheads as well as those.
973
00:47:47.663 --> 00:47:49.350
Okay.
974
00:47:49.350 --> 00:47:53.643
So going back to the beginning of what you were saying,
975
00:47:54.690 --> 00:47:59.690
how will that impact NRC's GTAS reconciliation?
976
00:48:03.090 --> 00:48:04.863
Well, I think.
977
00:48:05.867 --> 00:48:08.010
I mean it's a low dollar amount,
978
00:48:08.010 --> 00:48:10.185
so overall it's not gonna have a high impact
979
00:48:10.185 --> 00:48:13.950
on our score card, so I'm not utterly, you know,
980
00:48:13.950 --> 00:48:17.396
overly concerned at this point in time, but you know,
981
00:48:17.396 --> 00:48:21.450
I'm a small agency so there could be bigger agencies.
982
00:48:21.450 --> 00:48:23.430
I understand, yeah, yep.
983
00:48:23.430 --> 00:48:24.843
It's an issue right now.
984
00:48:26.550 --> 00:48:30.993
So It is not an issue that's going to go away at this time.
985
00:48:33.014 --> 00:48:34.770
So are there any suggestions
986
00:48:34.770 --> 00:48:37.893
for those of us who are trying to do a reconciliation
987
00:48:37.893 --> 00:48:42.600
that we should look at, take into account, make note of?
988
00:48:42.600 --> 00:48:45.210
No, I think that, I mean for me,
989
00:48:45.210 --> 00:48:47.670
I would say couple things.
990
00:48:47.670 --> 00:48:50.493
If we get the limits in G-Invoicing,
991
00:48:51.330 --> 00:48:55.470
they're already listed on any members or agreements,
992
00:48:55.470 --> 00:48:57.656
on IPEC, they're in various locations,
993
00:48:57.656 --> 00:49:01.473
so I couldn't direct you to an exact location,
994
00:49:02.400 --> 00:49:06.285
but I would make note of it in G-Invoicing
995
00:49:06.285 --> 00:49:11.285
and maybe, I mean to me, that's where you start, right?
996
00:49:12.630 --> 00:49:13.463
Knowledge.
997
00:49:13.463 --> 00:49:17.730
So then the next question is when you put input agreements,
998
00:49:17.730 --> 00:49:22.730
are you inputting the limit/SAHI in into your system?
999
00:49:24.450 --> 00:49:26.340
I mean, to me that's the biggest issue
1000
00:49:26.340 --> 00:49:28.410
that people don't recognize.
1001
00:49:28.410 --> 00:49:29.613
Agencies don't recognize a number
1002
00:49:29.613 --> 00:49:32.340
that they don't use, right?
1003
00:49:32.340 --> 00:49:34.890
And so where does it belong?
1004
00:49:34.890 --> 00:49:35.730
What is it?
1005
00:49:35.730 --> 00:49:37.110
Do I really need to record it?
1006
00:49:37.110 --> 00:49:38.553
And is it being recorded?
1007
00:49:39.780 --> 00:49:42.840
And so I would, I mean, that's...
1008
00:49:42.840 --> 00:49:45.453
And I think that G-Invoicing will help in that.
1009
00:49:46.920 --> 00:49:49.260
I hope that it's clearly delineated in there
1010
00:49:49.260 --> 00:49:53.911
when we are filling out our G-Invoicing forms.
1011
00:49:53.911 --> 00:49:57.003
I think that's a start to help.
1012
00:50:00.120 --> 00:50:02.798
Certainly we can talk, I mean you can call me anytime
1013
00:50:02.798 --> 00:50:07.173
and I'll reach out and we can talk further.
1014
00:50:09.390 --> 00:50:11.337
Okay, not to cut you off Angela,
1015
00:50:11.337 --> 00:50:14.721
but we do have one other hand up for Felicia Ford Jones
1016
00:50:14.721 --> 00:50:16.263
and I do wanna get to that.
1017
00:50:17.670 --> 00:50:18.630
Good morning again,
1018
00:50:18.630 --> 00:50:23.630
I think that you answered this question, but I wasn't clear,
1019
00:50:24.047 --> 00:50:26.990
so I thought I would just re-ask
1020
00:50:26.990 --> 00:50:30.360
just to make sure that I'm clear in my head.
1021
00:50:30.360 --> 00:50:33.930
And the question had to do with the cutoff dates.
1022
00:50:33.930 --> 00:50:38.171
So I'm thinking is this report going to be official
1023
00:50:38.171 --> 00:50:40.680
as of a certain date?
1024
00:50:40.680 --> 00:50:44.580
Because I had some concerns before
1025
00:50:44.580 --> 00:50:49.530
because while G-Invoicing has its plus three
1026
00:50:50.400 --> 00:50:54.273
or at the end of the year, plus five cutoff dates,
1027
00:50:55.350 --> 00:50:59.190
GTAS has extension dates that could go, you know,
1028
00:50:59.190 --> 00:51:02.070
four business days or more out
1029
00:51:02.070 --> 00:51:04.410
depending on whether it's a month-end
1030
00:51:04.410 --> 00:51:06.330
or at the end of the year.
1031
00:51:06.330 --> 00:51:09.090
And I wondered how that is, you know,
1032
00:51:09.090 --> 00:51:11.086
accounted for in this reporting.
1033
00:51:11.086 --> 00:51:15.150
Is there a cutoff date that this is, you know,
1034
00:51:15.150 --> 00:51:19.290
that we should pull this report or how does that work?
1035
00:51:19.290 --> 00:51:23.130
And then I want to piggyback,
1036
00:51:23.130 --> 00:51:26.010
you had mentioned that the limit issue
1037
00:51:26.010 --> 00:51:30.810
is an internal issue to, you know, the military,
1038
00:51:30.810 --> 00:51:34.370
but it actually impacts those agencies
1039
00:51:34.370 --> 00:51:38.040
that do business with them and that in GTAS,
1040
00:51:38.040 --> 00:51:41.313
we don't have a way of reporting the limits.
1041
00:51:43.350 --> 00:51:46.653
And so those are the two things I wanted to mention.
1042
00:51:46.653 --> 00:51:48.540
So I can jump on the first question, Felicia,
1043
00:51:48.540 --> 00:51:50.580
and then we can kind of follow up on the second question.
1044
00:51:50.580 --> 00:51:52.352
So the first question, I know you kind of hit on
1045
00:51:52.352 --> 00:51:55.740
and I hit on it earlier as far as G-Invoicing
1046
00:51:55.740 --> 00:51:58.290
has a plus three and we'll interface the information in
1047
00:51:58.290 --> 00:51:59.790
from G-Invoicing and the GTAS
1048
00:51:59.790 --> 00:52:01.650
before the reporting window opens up
1049
00:52:01.650 --> 00:52:04.917
for the specific period for GTAS.
1050
00:52:04.917 --> 00:52:07.590
But like you mentioned, a reporting window in GTAS,
1051
00:52:07.590 --> 00:52:09.288
usually right now the new standard schedule
1052
00:52:09.288 --> 00:52:12.480
is we open up on the fourth business day of the month
1053
00:52:12.480 --> 00:52:15.750
and we have 10 business days for reporting happening
1054
00:52:15.750 --> 00:52:18.318
and then we have an extension window on quarter ends
1055
00:52:18.318 --> 00:52:19.720
for any proprietary corrections
1056
00:52:19.720 --> 00:52:21.833
during that extension window.
1057
00:52:21.833 --> 00:52:25.011
So I guess recommendation on that is you can run the report,
1058
00:52:25.011 --> 00:52:28.470
the report will be updated as you certify
1059
00:52:28.470 --> 00:52:30.030
and upload new information
1060
00:52:30.030 --> 00:52:31.260
during the GTAS reporting windows.
1061
00:52:31.260 --> 00:52:33.900
So you can run it during the window to kind of check that,
1062
00:52:33.900 --> 00:52:35.520
see if there's any corrections you need to make
1063
00:52:35.520 --> 00:52:38.010
in your ATB reporting during the GTAS window
1064
00:52:38.010 --> 00:52:39.840
before that window closes.
1065
00:52:39.840 --> 00:52:43.560
But if you're really looking for a final report out
1066
00:52:43.560 --> 00:52:46.590
on GTAS for the G-Invoicing and GTAS comparison report,
1067
00:52:46.590 --> 00:52:48.630
I'll run that after the extension window closes
1068
00:52:48.630 --> 00:52:50.627
or you guys know you're done with your reporting
1069
00:52:50.627 --> 00:52:52.789
'cause you know the G-Invoicing information
1070
00:52:52.789 --> 00:52:57.660
is not going to change, but obviously that GTAS information
1071
00:52:57.660 --> 00:53:00.570
can change up until the end of the extension window
1072
00:53:00.570 --> 00:53:01.420
on a quarter-end.
1073
00:53:04.350 --> 00:53:05.670
Thank you.
1074
00:53:05.670 --> 00:53:10.670
And then the GTAS limits, that was just the comment so.
1075
00:53:11.037 --> 00:53:13.070
Yeah, and so I mean, I was just thinking of that
1076
00:53:13.070 --> 00:53:14.790
as Lisa was talking through that as well.
1077
00:53:14.790 --> 00:53:19.170
But really for the limit, is that more of a,
1078
00:53:19.170 --> 00:53:22.230
I mean the limit's gonna be more
1079
00:53:22.230 --> 00:53:23.740
on the IGT difference side
1080
00:53:23.740 --> 00:53:26.280
than not a G-Invoicing compliance side, right?
1081
00:53:26.280 --> 00:53:28.710
I mean, 'cause really, from what I hear there,
1082
00:53:28.710 --> 00:53:31.140
it's shared TAs in identifying the correct training partner
1083
00:53:31.140 --> 00:53:33.930
within a shared TAS and having that limit available
1084
00:53:33.930 --> 00:53:35.640
to properly reconcile
1085
00:53:35.640 --> 00:53:37.770
which training partner you're trading with
1086
00:53:37.770 --> 00:53:39.690
to make sure your IGT differences
1087
00:53:39.690 --> 00:53:41.820
are eliminated as much as possible.
1088
00:53:41.820 --> 00:53:44.160
But really, I mean, when we're looking at it
1089
00:53:44.160 --> 00:53:46.140
at a holistic view on a scorecard purposes,
1090
00:53:46.140 --> 00:53:48.930
it's at a holistic FR entity level
1091
00:53:48.930 --> 00:53:53.730
that we're rolling up that 097s or those shared TAS up into.
1092
00:53:53.730 --> 00:53:55.352
So anything that has a shared TAS
1093
00:53:55.352 --> 00:53:59.610
should roll up into that report for that FR entity.
1094
00:53:59.610 --> 00:54:02.340
But the limit, I know it's something we need to look at
1095
00:54:02.340 --> 00:54:04.380
and address, but I just wanna make sure
1096
00:54:04.380 --> 00:54:06.060
I'm understanding that correctly.
1097
00:54:06.060 --> 00:54:08.640
It's more of a training partner issue
1098
00:54:08.640 --> 00:54:10.642
to making sure that you are trading
1099
00:54:10.642 --> 00:54:12.060
with the correct partner
1100
00:54:12.060 --> 00:54:15.303
and eliminating those IGT differences as much as possible.
1101
00:54:17.190 --> 00:54:18.023
Yes.
1102
00:54:19.290 --> 00:54:20.123
Okay.
1103
00:54:20.123 --> 00:54:21.510
Yeah, that's my understanding as well
1104
00:54:21.510 --> 00:54:23.310
and I know that that is an ongoing issue
1105
00:54:23.310 --> 00:54:28.061
that we are looking at it and note, we are aware of that,
1106
00:54:28.061 --> 00:54:29.583
we need to look at, but just wanna make sure
1107
00:54:29.583 --> 00:54:32.010
that I was clear on that, 'cause in my mind,
1108
00:54:32.010 --> 00:54:34.140
I was making sure my understanding was
1109
00:54:34.140 --> 00:54:35.820
it's not really a G-Invoicing compliance issue
1110
00:54:35.820 --> 00:54:38.319
and a metric issue, it's more of a trading partner
1111
00:54:38.319 --> 00:54:42.513
IGT elimination issue that we're talking about.
1112
00:54:45.300 --> 00:54:47.640
Okay, we do have one-
So that's.
1113
00:54:47.640 --> 00:54:48.840
Sorry Alex.
1114
00:54:48.840 --> 00:54:50.710
I was gonna say we do have one more hand up
1115
00:54:50.710 --> 00:54:52.740
and it's Lisa Sawenko.
1116
00:54:52.740 --> 00:54:53.880
I'm gonna try to squeeze that in,
1117
00:54:53.880 --> 00:54:56.610
'cause we're right at the end of our time slot here.
1118
00:54:56.610 --> 00:54:58.560
But for anyone else that has unanswered questions,
1119
00:54:58.560 --> 00:55:01.120
I'm gonna drop a email address in chat.
1120
00:55:01.120 --> 00:55:03.120
Feel free to send them there.
1121
00:55:03.120 --> 00:55:05.370
And then Lisa, I'm gonna turn it over to you.
1122
00:55:10.800 --> 00:55:12.270
Can you hear me?
1123
00:55:12.270 --> 00:55:13.320
Yep.
1124
00:55:13.320 --> 00:55:15.690
Okay, so this is Lisa Sawenko
1125
00:55:15.690 --> 00:55:17.430
from the Department of Veterans Affairs.
1126
00:55:17.430 --> 00:55:18.767
I typed a question in the chat.
1127
00:55:18.767 --> 00:55:22.620
So how does this work, this reconciliation,
1128
00:55:22.620 --> 00:55:23.610
and then these edits?
1129
00:55:23.610 --> 00:55:26.583
I know right now, you're saying they're gonna be proposed,
1130
00:55:27.450 --> 00:55:30.073
which at some point I'm assuming in the very near future,
1131
00:55:30.073 --> 00:55:32.790
they will become fatal.
1132
00:55:32.790 --> 00:55:35.383
How is this gonna work for those agencies
1133
00:55:35.383 --> 00:55:38.160
that aren't in G-Invoicing yet
1134
00:55:38.160 --> 00:55:40.860
as far as the reconciliation goes?
1135
00:55:40.860 --> 00:55:44.756
Because obviously if we're compliant on our side,
1136
00:55:44.756 --> 00:55:46.683
but one of our, you know,
1137
00:55:48.000 --> 00:55:50.325
on the other side isn't in G-Invoicing,
1138
00:55:50.325 --> 00:55:53.160
how is this working?
1139
00:55:53.160 --> 00:55:54.660
Yeah, that's a very good question Lisa
1140
00:55:54.660 --> 00:55:55.950
and I know it's something that we've thought
1141
00:55:55.950 --> 00:55:56.783
about in the past.
1142
00:55:56.783 --> 00:55:59.520
But ultimately, if your training partner
1143
00:55:59.520 --> 00:56:00.548
isn't in G-Invoicing,
1144
00:56:00.548 --> 00:56:02.640
that activity's not going through G-Invoicing,
1145
00:56:02.640 --> 00:56:04.478
it's going to lead to a difference
1146
00:56:04.478 --> 00:56:06.840
between what's happening in your GTAS reporting
1147
00:56:06.840 --> 00:56:09.540
and what's actually being G-Invoicing.
1148
00:56:09.540 --> 00:56:12.290
So I mean as you pull these reports and do that,
1149
00:56:12.290 --> 00:56:13.890
do those reconciliations,
1150
00:56:13.890 --> 00:56:15.360
that's something I think you could call out
1151
00:56:15.360 --> 00:56:18.900
and say, "Hey for VA, if we were transacting with,"
1152
00:56:18.900 --> 00:56:20.512
I'll say like DOI for example,
1153
00:56:20.512 --> 00:56:22.380
they're not currently in G-Invoicing,
1154
00:56:22.380 --> 00:56:24.990
we know that's a spot where the activity
1155
00:56:24.990 --> 00:56:27.600
is flowing into GTAS but we don't have that activity
1156
00:56:27.600 --> 00:56:30.060
in G-Invoicing and that's a portion of our activity
1157
00:56:30.060 --> 00:56:32.651
that's not being captured in our overall compliance metric
1158
00:56:32.651 --> 00:56:34.650
for G-Invoicing.
1159
00:56:34.650 --> 00:56:36.717
So we know those examples are happening
1160
00:56:36.717 --> 00:56:39.600
and those are probably conversation pieces we're gonna have
1161
00:56:39.600 --> 00:56:40.680
during the scorecard meetings
1162
00:56:40.680 --> 00:56:43.890
to talk about your G-Invoicing compliance metric
1163
00:56:43.890 --> 00:56:46.139
and talk about, "Hey, some of the issues that we see,"
1164
00:56:46.139 --> 00:56:48.930
is whether that's training partner readiness
1165
00:56:48.930 --> 00:56:50.824
and other things, but we know that is going to be an issue
1166
00:56:50.824 --> 00:56:52.380
and that is going to be reflected
1167
00:56:52.380 --> 00:56:55.521
as far as a difference between what's being reported in GTAS
1168
00:56:55.521 --> 00:56:58.437
and what's being transacted in G-Invoicing.
1169
00:56:59.335 --> 00:57:02.100
Okay, and then I know,
1170
00:57:02.100 --> 00:57:04.318
I believe it was Robert responded to my other question
1171
00:57:04.318 --> 00:57:06.327
as far as this is only available currently
1172
00:57:06.327 --> 00:57:11.327
in the G-Invoicing, but because this is in relation to IGOV
1173
00:57:11.902 --> 00:57:14.940
and IGC or IGT differences,
1174
00:57:14.940 --> 00:57:18.293
it would really be beneficial if this report somehow
1175
00:57:18.293 --> 00:57:22.877
was available in the GTAS side similar to the IGOV reports
1176
00:57:22.877 --> 00:57:25.578
that we have now to check all our reciprocating categories
1177
00:57:25.578 --> 00:57:28.833
because this ultimately would flow into there.
1178
00:57:30.990 --> 00:57:33.030
So make sure, I'm on the same page there
1179
00:57:33.030 --> 00:57:36.270
with you Lisa, I know the GTAS reporting functionality
1180
00:57:36.270 --> 00:57:39.150
is out there currently, but as far as the IGOV piece,
1181
00:57:39.150 --> 00:57:40.828
what do you actually meaning there as far as-
1182
00:57:40.828 --> 00:57:43.260
Like to be able to see the details
1183
00:57:43.260 --> 00:57:44.850
on the G-Invoicing side.
1184
00:57:44.850 --> 00:57:45.884
I don't have access,
1185
00:57:45.884 --> 00:57:49.350
nor I don't need access to G-Invoicing.
1186
00:57:49.350 --> 00:57:51.690
So for me to be able to get this report,
1187
00:57:51.690 --> 00:57:56.670
obviously I can coordinate with my team
1188
00:57:56.670 --> 00:57:58.860
that works the intergovernmental stuff
1189
00:57:58.860 --> 00:58:01.678
and G-Invoicing to obtain the report,
1190
00:58:01.678 --> 00:58:03.152
but it'd be beneficial to be able
1191
00:58:03.152 --> 00:58:05.851
to not only see the IGOV report,
1192
00:58:05.851 --> 00:58:08.640
but then be able to see the other side
1193
00:58:08.640 --> 00:58:12.660
that the G-Invoicing piece that might be causing this,
1194
00:58:12.660 --> 00:58:13.860
you know, the difference,
1195
00:58:13.860 --> 00:58:15.963
the reciprocating category difference.
1196
00:58:21.270 --> 00:58:22.950
Okay, yeah, we can definitely look at that
1197
00:58:22.950 --> 00:58:25.560
and see if we can help you as far
1198
00:58:25.560 --> 00:58:26.859
as getting access to G-Invoicing
1199
00:58:26.859 --> 00:58:28.959
or somehow getting those reports out there
1200
00:58:30.660 --> 00:58:32.430
to help out that issue, talking about Lisa.
1201
00:58:32.430 --> 00:58:35.069
But we can definitely talk more about that offline
1202
00:58:35.069 --> 00:58:38.343
and see what kind of solution we can come up with for that.
1203
00:58:41.910 --> 00:58:44.040
Okay, well with that being said,
1204
00:58:44.040 --> 00:58:47.940
we are over time so just wanna respect everyone's calendars.
1205
00:58:47.940 --> 00:58:50.730
So thank you for your participation today.
1206
00:58:50.730 --> 00:58:52.013
Again, if you had questions
1207
00:58:52.013 --> 00:58:54.960
that we didn't get to or did not answer,
1208
00:58:54.960 --> 00:58:57.960
I did drop an email in chat
1209
00:58:57.960 --> 00:59:00.049
and then this is a recorded session
1210
00:59:00.049 --> 00:59:03.840
and we will make it available on the fiscal service website.
1211
00:59:03.840 --> 00:59:05.094
When we're able to publish that,
1212
00:59:05.094 --> 00:59:07.530
I will send out a note for everyone.
1213
00:59:07.530 --> 00:59:10.290
So thank you for your participation today again
1214
00:59:10.290 --> 00:59:12.273
and have a great rest of your week.
1215
00:59:15.600 --> 00:59:16.673
Thanks everyone.